-
Notifications
You must be signed in to change notification settings - Fork 56
Support different "originators" of member invitations #623
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
Comments
@maxceem looks good to me we are not much altering the flow except the new optional param
|
@RishiRajSahu on the one hand it would be technically easier. But I can see many places which has to be updated depend on the
So to update all these places we would have put many conditions across the templates to check if it's TaaS or Connect app. And if tomorrow we add the 3rd application, these conditions would become even more complex. So to make the logic general and straightforward I suggest create folders per each But, at the end all these templates would be combined into one single template which we add to the Sendgrid, which would look like this:
|
The requirements in TaaS App have been changed, so we don't need this anymore. |
Context
We have functionality to invite members to the Topcoder Projects inside Connect App which looks like this. When users are invited they also receive a email notifications with links to accept or decline invitation as on screenshot. This email is styled for Connect App, and links to decline and accept invitation lead to Connect App. At the moment we are implementing functionality to invite members to the same Topcoder Projects inside another application called TaaS App. It uses the same Projects API to invite members. As a result user get the same emails with links to Connect App.
General Task
We have to update Projects API and related services so when invited members we can indicate which application invited members so users would get different email notifications with links and styles for the corresponding application Connect App or TaaS App.
Current Workflow
Task Details
The text was updated successfully, but these errors were encountered: