unionlabs/union

implement proper child->parent relationships in queue implementations

Opened this issue · 0 comments

we don't currently handle this at all in either `pg-queuee:

// TODO: Handle parent ids properly

// TODO: Handle parent ids properly

for the in-memory queue the logic is written, but i have little to no faith in it's implementation as it is largely untested:

impl<T: QueueMessage> Queue<T> for InMemoryQueue<T> {

rather than duplicating this logic between both implementations, we should perhaps revisit the Queue<T> abstraction and see if we can come up with a better design.

it would also be helpful if we provided some sort of testing framework for plugin authors to test their implementations of run_pass to ensure that they're handling ids properly.