Skip to content
This repository was archived by the owner on Jan 4, 2022. It is now read-only.

Conversation

@malev
Copy link
Member

@malev malev commented May 4, 2013

I think that the enqueue action should be handle by who
needs it, so it does not belongs to this project.
I'm starting to move this behaviour into a service and with
that said I think that the service should be responsable on
asking for an enqueue.
Also, I don't think that enqueue should be a private method.
Maybe we need to handle this action from an admin page.

Do not merge till we merge the new services into webapp

I think that the enqueue action should be handle by who
needs it, so it does not belongs to this project.
I'm starting to move this behaviour into a service and with
that said I think that the service should be responsable on
asking for an enqueue.
Also, I don't think that enqueue should be a private method.
Maybe we need to handle this action from an admin page.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants