Notification page implemented resolves enhacement request #546

[saltykheera]

#546
#546
notification are categeorizes in two section
A> unread
b> inbox
inbox consist of all the notification user has requested where as
unread consist of notification which are not read

[marcgc21]

I think that we are moving to a nice update of the system! However, I still have concerns about those notifications dissapearing.

Can you update the system to avoid cleaning the notifications? Right now I'm not sure if it is a database delete or it is just a filter state on the render visualization. Can you confirm that?

[marcgc21]

@saltykheera Also, try to update from the develop branch, I think that it solves part of the problems of the CI pipeline!

[saltykheera]

I think that we are moving to a nice update of the system! However, I still have concerns about those notifications dissapearing.

Can you update the system to avoid cleaning the notifications? Right now I'm not sure if it is a database delete or it is just a filter state on the render visualization. Can you confirm that?

the notification once read are deleted
and are not saved in database
hence , the past notifications can't be recovered but after this pr is merged
the notification will then start to get stored in the database

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE