Add polling for vulnerability comments and state
What does this MR do?
Add polling for vulnerability comments and state
- add polling component for comments
- refetch discussions if a note with unknown discussion id comes in
- update X-Last-Fetched-At to only get latest comments
- use newly available discussion url and notes url for updates
Screenshots
In the video below, I demonstrate how if one user updates a note, adds a note, or adds a new discusssion, the other user sees the changes a short time later
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #214595 (closed) Related to !30244 (merged)
Edited by Alexander Turinske