-
Notifications
You must be signed in to change notification settings - Fork 38
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
Improve system notifications #237
Comments
This requires some more thought. We filter projects on the server and we allow the user to select which projects are interesting. To be able to correctly identify all project transitions we would need to return all projects and filter on the client. This however could result in a huge amount of additional data being sent between the client and server. Edit: We could also figure out transitions server side and have a the transition in the response. This however would still require the request to include all the previously fetched projects as the server is stateless. We do currently send the IDs of all the previously seen projects so the "include new projects" feature works so this still might be a better idea. By default we only filter out healthy projects, so in that case we could assume missing projects are healthy. Which realistically is probably safe, but in theory they could have actually been removed from the server. However this approach no longer works if the filter has been changed to filter out more that one prognosis, and it also feels like the code could get quite messy. |
Some ideas for improving system notifications:
The text was updated successfully, but these errors were encountered: