Skip to content

[feat] Display guideline levels in the guideline statistics table#4787

Open
bruntib wants to merge 1 commit intoEricsson:masterfrom
bruntib:guideline_level
Open

[feat] Display guideline levels in the guideline statistics table#4787
bruntib wants to merge 1 commit intoEricsson:masterfrom
bruntib:guideline_level

Conversation

@bruntib
Copy link
Copy Markdown
Contributor

@bruntib bruntib commented Feb 24, 2026

Some guidelines have their own severity ranking, like the levels at SEI-CERT. In this commit these are also displayed at the guideline statistics table.

@bruntib bruntib added this to the release 6.28.0 milestone Feb 24, 2026
Some guidelines have their own severity ranking, like the levels at
SEI-CERT. In this commit these are also displayed at the guideline
statistics table.
@bruntib bruntib marked this pull request as ready for review March 24, 2026 22:26
@bruntib bruntib requested a review from vodorok as a code owner March 24, 2026 22:26
1: string ruleId, // The identifier of the rule.
2: string title, // The rule summary.
3: string url, // The link of the rule page.
4: list<string> checkers, // List of checker names,
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
4: list<string> checkers, // List of checker names,
4: list<string> checkers, // List of checker names.

2: string title, // The rule summary.
3: string url, // The link of the rule page.
4: list<string> checkers, // List of checker names,
5: optional string level,
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a description what level is and why is it optional.

Copy link
Copy Markdown
Collaborator

@gulyasgergely902 gulyasgergely902 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If not required in the next release, please, wait with this until the migration is complete to Vue 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants