-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
fix(api-service): translation groups causing long response time in v2 create/update workflow #7450
fix(api-service): translation groups causing long response time in v2 create/update workflow #7450
Conversation
… create/update workflow
✅ Deploy Preview for dashboard-v2-novu-staging ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for dev-web-novu ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
(process.env.NOVU_ENTERPRISE === 'true' || | ||
process.env.CI_EE_TEST === 'true') && | ||
storedWorkflow.origin === WorkflowOriginEnum.NOVU_CLOUD_V1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only run the translation analytics code in v1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we should not load the translations during the message sent in the SendMessageBase
usecase, but I haven't added any logic there because there is no workflow information at that stage, like the NotificationStepEntity
is missing the workflow
info and particularly the origin
field.
To do that, it might require more work.
What changed? Why was the change needed?
The Translation Groups (TranslationService) are causing slow response time. The translations code is not relevant in v2.
Screenshots
Expand for optional sections
Related enterprise PR
Special notes for your reviewer