-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add settings endpoint for web/push and e-mail notifications #9
Comments
Hi @donni106 |
For now it would be email only. |
Hi @donni106 |
All right, I will talk to my colleagues about a decision. And what about the second question?
|
Hi @donni106 |
Hi @donni106 |
we do not need the checkbox about desktop notifications. |
Hi @donni106 |
please do it together directly. so we will be able to change settings for web/push and email. |
We are updated space, email and web notification setting Working flow of space notification setting 1. Pass space id in body data for adding space in space notification. 2. If user is the member of that space only then space is added for the user. 3. Otherwise, it will throw an error. 4. In other word, if user status will be 1(invited) or 2(applicant) for that space ,it will throw an error Working flow of email notification setting 1. pass the email key name with status (true/false) to update the email notification setting 2. Check the module is active or not 3. Check the key value is disabled or not (which mean check we can update the value or not) 4. Validate the input values (that is only true,false ,0 and 1 are accepted) 5. Update the email notification setting Same working flow for web notification also
We are updated space, email and web notification setting Working flow of space notification setting 1. Pass space id in body data for adding space in space notification. 2. If user is the member of that space only then space is added for the user. 3. Otherwise, it will throw an error. 4. In other word, if user status will be 1(invited) or 2(applicant) for that space ,it will throw an error Working flow of email notification setting 1. pass the email key name with status (true/false) to update the email notification setting 2. Check the module is active or not 3. Check the key value is disabled or not (which mean check we can update the value or not) 4. Validate the input values (that is only true,false ,0 and 1 are accepted) 5. Update the email notification setting Same working flow for web notification also
We are updated space, email and web notification setting Working flow of space notification setting 1. Pass space id in body data for adding space in space notification. 2. If user is the member of that space only then space is added for the user. 3. Otherwise, it will throw an error. 4. In other word, if user status will be 1(invited) or 2(applicant) for that space ,it will throw an error Working flow of email notification setting 1. pass the email key name with status (true/false) to update the email notification setting 2. Check the module is active or not 3. Check the key value is disabled or not (which mean check we can update the value or not) 4. Validate the input values (that is only true,false ,0 and 1 are accepted) 5. Update the email notification setting Same working flow for web notification also
HumHub provides settings per user for e-mail notification, which can be edited in the web:
We need
/settings
endpoints to list and update settings for e-mail notifications.The text was updated successfully, but these errors were encountered: