Replies: 1 comment
-
@chaporgin The biggest problem with that right now is that River UI doesn't actually know anything about your Go code, so it doesn't know which types of jobs should be available or what args they should take. I suppose what we could do is select distinct job kinds based on what's already in the database and give you a freeform override field in case you want to enqueue a job kind that's not already in there, but we'd probably still have to provide a raw JSON field, which isn't super great. I guess there could also be an option for when running the UI as a handler from your own code to have it take a workers bundle so it could know what's available. That might restrict it's usefulness though since probably not too many people go down that path. I agree though that this would be a useful feature in general though. |
Beta Was this translation helpful? Give feedback.
-
Hi! I have just started looking at the implementation of the river and the UI. It seems to be a great product; thank you very much!
I have a feature request: an ability to queue jobs from inside the UI. Have you been considering something like that?
Beta Was this translation helpful? Give feedback.
All reactions