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

[Feature request] Ignore some messages by regex #223

Closed
dalance opened this issue Oct 4, 2024 · 3 comments · Fixed by #229
Closed

[Feature request] Ignore some messages by regex #223

dalance opened this issue Oct 4, 2024 · 3 comments · Fixed by #229

Comments

@dalance
Copy link

dalance commented Oct 4, 2024

I uses cargo:warning to inform some messages in build.rs.
This is because cargo:info is not supported yet. ( rust-lang/cargo#7037 )

bacon handles these messages as warning, but it can't be resolved.
So I think message filtering by regex may be useful.

For example, an actual message is like below:

warning: veryl-std@0.13.0: std hash: 158094aee3b99767fbd3cf75a1be02bf31a4aa5215dc39053c4e81a3b6617b8b

I expect the above message is ignored by a configuration like below

ignore_messages = ["warning: veryl-std@.*"]
@Canop
Copy link
Owner

Canop commented Oct 4, 2024

Can you please build a minimal project demonstrating the problem ?

@dalance
Copy link
Author

dalance commented Oct 4, 2024

Please refer https://github.com/dalance/demo_for_bacon

Canop added a commit that referenced this issue Oct 5, 2024
@Canop Canop mentioned this issue Oct 5, 2024
@Canop Canop closed this as completed in #229 Oct 6, 2024
Canop added a commit that referenced this issue Oct 6, 2024
The `ignored_lines` field can be defined either at the root of a config file or in a specific job.

If defines a set of regular expressions specifying the lines which should not be interpreted by the analyzer.

Fix #223
@dalance
Copy link
Author

dalance commented Oct 7, 2024

Thank you!

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 a pull request may close this issue.

2 participants