[feature] Add REST API to manage notification preferences of other users
nemesifier opened this issue · 1 comments
We need a REST API endpoint which will allow administrators to change the notification settings of other users.
The API endpoint path could be: /api/v1/users/user/{id}/notification-setting/ or if that proves to be hard to implement due to the modular structure of OpenWISP, we could use /api/v1/notification/user/{id}/setting/ (althought the former is preferred).
Only superusers shall be able to use this API endpoint.
The logic of this API endpoint must be shared with the logic of the existing /api/v1/notification/user-settings/ and avoid duplication.
We need a REST API endpoint which will allow administrators to change the notification settings of other users.
The API endpoint path could be:
/api/v1/users/user/{id}/notification-setting/or if that proves to be hard to implement due to the modular structure of OpenWISP, we could use/api/v1/notification/user/{id}/setting/(althought the former is preferred).Only superusers shall be able to use this API endpoint.
The logic of this API endpoint must be shared with the logic of the existing
/api/v1/notification/user-settings/and avoid duplication.
Just to make it more explicit. I am writing the GSOC proposal and trying to catch up the instruction, in the instruction text, the below two apis path should be corrected.
/api/v1/notification/user/{id}/setting/ => /api/v1/notifications/notification/user/{id}/setting/
/api/v1/notification/user-settings/ => /api/v1/notifications/notification/user-setting/ no 's' in the end.