Skip to content
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

Add warning category #129

Merged
merged 4 commits into from
Feb 16, 2023
Merged

Add warning category #129

merged 4 commits into from
Feb 16, 2023

Conversation

Honny1
Copy link
Member

@Honny1 Honny1 commented Feb 3, 2023

This PR adds a warning data class that contains the category and text of the warning.

@Honny1 Honny1 marked this pull request as ready for review February 3, 2023 17:30
@Honny1 Honny1 mentioned this pull request Feb 7, 2023
@Honny1 Honny1 force-pushed the add-warning-category branch 3 times, most recently from eec0d86 to bbdb8b6 Compare February 10, 2023 10:06
@jan-cerny jan-cerny self-assigned this Feb 13, 2023
@@ -178,7 +178,10 @@
<i class="fas fa-fw fa-exclamation-triangle" aria-hidden="true"></i>
</div>
<div class="pf-c-alert__title">
{{- warning | set_css_for_list -}}
Warning category:&nbsp;{{- warning.category | capitalize -}}
Copy link
Member

Choose a reason for hiding this comment

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

This looks ugly. Keep only Warning as a title. Put the category value to a box or under the heading and don't use the "category" word at all.

Copy link
Member Author

Choose a reason for hiding this comment

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

What about using the <category> warning format? As it is in the picture.
image

Copy link
Member

Choose a reason for hiding this comment

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

That sounds great!

Copy link
Member

@jan-cerny jan-cerny left a comment

Choose a reason for hiding this comment

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

I have generated the report and I have seen the warnings.

@jan-cerny jan-cerny merged commit 322a4f5 into OpenSCAP:main Feb 16, 2023
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.

None yet

2 participants