feat(ui): filter functionality for warnings#27
Open
sallto wants to merge 1 commit intogoblint:masterfrom
Open
Conversation
Filter warnings according to severity and wether they originate from the current file
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
1 participant
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.
Filter warnings according to severity and wether they originate from the current file
automatic type deduction fails for severity_to_bootstrap_class, therefore the type annotation is necessary.
Linearly filtering the whole warning list is quite slow for larger projects (100+ files) therefore the assignment to categories is precomputed in an array at mount time and memoized