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

feat: filtered check flags #139

Open
Chezka109 opened this issue Oct 22, 2024 · 3 comments · May be fixed by #150
Open

feat: filtered check flags #139

Chezka109 opened this issue Oct 22, 2024 · 3 comments · May be fixed by #150

Comments

@Chezka109
Copy link
Collaborator

Description: The current implementation of the check flag feature does not provide a mechanism to display only failing checks, specific checks of interest, or exclude certain checks from the output. This results in a cluttered view of all checks, making it difficult for users to quickly identify issues that require attention.

Expected Behavior: When the check flag is invoked, it should allow users to specify parameters that filter the results to show only failing checks, include checks of interest, and exclude certain checks based on user-defined criteria. This would streamline the feedback process, enabling users to focus on relevant failures without being overwhelmed by other check results.

Actual Behavior: The current check flag outputs all checks regardless of their status, leading to confusion and a longer time required to identify and address issues.

Proposed Solution: Enhance the check flag feature to accept parameters that:

Show only failing checks.
Allow users to specify which checks to include in the output.
Provide an option to exclude certain checks from the output. This can be achieved by updating the command-line interface to accept filtering options, thereby improving usability and efficiency in identifying and resolving issues.

@gkapfham
Copy link
Collaborator

Hello @Chezka109 can you please give several concrete examples of this in the form of screenshots or segments of program output that are connected to command-line arguments?

@Chezka109 Chezka109 linked a pull request Oct 31, 2024 that will close this issue
3 tasks
@boulais01
Copy link
Collaborator

@Chezka109 Would you mind responding to Prof. Kapfhammer's request, or stating if the requested information is in the linked PR?

@Chezka109
Copy link
Collaborator Author

@boulais01 the requested information is in the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants