-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(heureka): renames Issues to Vulnerabilities tab with the default filter of issueType is Vulnerability #660
Conversation
🦋 Changeset detectedLatest commit: ff1ef3e The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left one comment as a question
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM please ask someone to review it proper
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks logical to me!
Summary
This pull request introduces a default filter of
issueType=Vulnerability
to theissueMatches
entity, ensuring that only vulnerabilities associated with various images are displayed on this view. Additionally, related text updates have been implemented for consistency and clarity.Changes Made
issueType=Vulnerability
filter.issueType
filter option has been removed from the proposed filter select list, reflecting the default filtering logic applied.setQueryOption
function has been modified to merge new queryOptions with the existing ones rather than replacing them entirely.Related Issues
Checklist