Use unique fields for project list metrics columns - #686
Merged
Conversation
Signed-off-by: mykter <git@mykter.com>
nscuro
approved these changes
Dec 21, 2023
nscuro
left a comment
nscuro
left a comment
Member
There was a problem hiding this comment.
Thanks for yet another much appreciated fix!
heyiamwahab236
pushed a commit
to tecan/frontend_custom
that referenced
this pull request
Jun 17, 2026
…tings Use unique fields for project list metrics columns
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR makes the vulnerabilities and policy violations use unique field IDs in the bootstrap table spec. The docs say:
The frontend also uses the field id to save which columns the user has marked as visible or not.
Addressed Issue
Fixes #608
Additional Details
Tested with vulnerabilities present and absent, and with policy violations absent or zero. I don't have a project handy that has any policy violations, but the behaviour shouldn't change based on >0 vs absent.
Checklist