Skip to content
This repository has been archived by the owner on Oct 16, 2022. It is now read-only.

Back+Front-end : Customisation du niveau de notifications #53

Closed
iv-stpn opened this issue Oct 30, 2021 · 0 comments
Closed

Back+Front-end : Customisation du niveau de notifications #53

iv-stpn opened this issue Oct 30, 2021 · 0 comments
Assignees
Labels
difficulty: easy Issues that are easy to finish. priority: lowest Issues that must be fixed or PRs that must be finished with the looowwwest priority. type: feature Issues/PRs that requests/adds a new feature.

Comments

@iv-stpn
Copy link
Contributor

iv-stpn commented Oct 30, 2021

Il doit y avoir plusieurs niveaux de notifications (cf. #52) possibles propres à un favori donné:

Notification pour chaque activité > Notification pour une nouvelle réponse > Notification pour une réponse validé/un avancement du post > Notification pour une fermeture de post

Ce niveau de notification devra décider de si une notification est envoyée à l'utilisateur lorsqu'il y'a une activité sur un post en bookmark

Ce niveau de notification doit être modifiable depuis l'espace où l'on peut consulter ses favoris (cf. #55)

@iv-stpn iv-stpn changed the title Customisation du niveau de notifications (front-end) Back+Front-end : Customisation du niveau de notifications Nov 11, 2021
@iv-stpn iv-stpn added difficulty: complex Issues that are quite complex to finish. priority: low Issues that must be fixed or PRs that must be finished and merged with low priority. scope: file-sharing type: feature Issues/PRs that requests/adds a new feature. difficulty: easy Issues that are easy to finish. and removed difficulty: complex Issues that are quite complex to finish. labels Nov 11, 2021
@iv-stpn iv-stpn added this to the Partie Forum milestone Nov 11, 2021
@noftaly noftaly removed this from the Partie Forum milestone Feb 11, 2022
@noftaly noftaly added priority: lowest Issues that must be fixed or PRs that must be finished with the looowwwest priority. and removed priority: low Issues that must be fixed or PRs that must be finished and merged with low priority. labels Feb 11, 2022
@noftaly noftaly closed this as completed Feb 11, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
difficulty: easy Issues that are easy to finish. priority: lowest Issues that must be fixed or PRs that must be finished with the looowwwest priority. type: feature Issues/PRs that requests/adds a new feature.
Projects
None yet
Development

No branches or pull requests

6 participants