How to cancel a particular job in version 5 now that UUID has been removed about swiftqueue

[lucas34]

In version 5 we changed the architecture to allow custom constraint. Information such as UUID are now owned by the constraint itself. The contraint is also registered only if necessary. Previously all constraint was registered for all the job which makes it inefficient.
https://github.com/lucas34/SwiftQueue/blob/master/Sources/SwiftQueue/Constraint%2BUniqueUUID.swift#L28

Would be possible to build a method to expose the UUID.

[pierceglennie]

I see. Thanks for letting me know. I'm a bit confused by the best approach for cancelling an individual job in the new version but for now I've got it working by:

• Generating a UUID before creating a job
• Adding this both as a parameter to the job (under the .with and as the ID for the .singleInstance constraint
• To cancel the job, I then get the UUID from the parameter and cancel with the .cancelOperations(uuid: ...) method

This works although it feels pretty clunky to me since the UUID is basically duplicated and I have to remember to include it as a parameter on job creation, otherwise there is no way to cancel it. I just can't see a better method since the UUID is otherwise not exposed anywhere so far as I can tell.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.