Refetch count list when vulnerabilities are updated
What does this MR do?
This MR emits introduces an event hub which emits an event when the vulnerabilities are updated so that other components can react to it. The reason why I chose to use an event hub was because the component tree level is deep so I wanted to avoid passing listeners around.
Screenshots (strongly suggested)
As you can see from the following GIF, the vulnerabilities count list (severities and their correspondent numbers) are refetched when the status of the vulnerability is changed:
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
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 #263819 (closed)