-
Notifications
You must be signed in to change notification settings - Fork 135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Agenda, background job worker from v1 to v2 #754
Comments
Do we already have an issue about the migration ES5 -> ES6+? It's been coming up on different occasions. It will need a change in linter and some period in which it will be ok to write the code in ES 2017. The |
This issue is marked as unloved because it has not had any activity for 180 days. It doesn't mean it's not important, so please remove the unloved label if you like it, or add a comment saying what it means to you :) If this was a bug, maybe you can test to see if this is still an issue? However, if you just leave it like this, I'll close it in 14 days to help keep your issues tidy! Thanks! |
Agenda v2 was a complete rewrite to support promises instead of callbacks.
Agenda is run in the background worker to process jobs. Main app and the worker run separately in parallel with
npm start
.v2 changelog: https://github.com/agenda/agenda/blob/master/History.md#200--2018-07-19
Rewrite needed mainly at:
modules/*/server/jobs/*.server.job.js
-filesI'm not sure if we should wait for ES5 → ES6 migration before updating Agenda, because we could jump directly using
async/await
-format (that we don't support at the moment).The text was updated successfully, but these errors were encountered: