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

[CLI] Add a way to filter error codes #11008

Closed
axic opened this issue Feb 24, 2021 · 4 comments
Closed

[CLI] Add a way to filter error codes #11008

axic opened this issue Feb 24, 2021 · 4 comments
Labels
closed due inactivity The issue/PR was automatically closed due to inactivity. low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact stale The issue/PR was marked as stale because it has been open for too long.

Comments

@axic
Copy link
Member

axic commented Feb 24, 2021

If we have #11006, that means framework can filter warnings/errors based on error codes. If we advocate/allow that, then we may want to consider adding a way to filter error codes on the command line, i.e. --ignore-errors <comma separated error codes>.

@axic
Copy link
Member Author

axic commented Feb 24, 2021

I am personally not fully sold on having this, but created the issue for completeness and a way to discuss this.

@chriseth
Copy link
Contributor

I'm also not fully sold. For casually calling solc *.sol, this is not required. If you do anything more fancy, then you probably use a framework that has a project settings file which can contain any filtering instructions the framework can do.

@cameel cameel added low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact labels Sep 27, 2022
@github-actions
Copy link

This issue has been marked as stale due to inactivity for the last 90 days.
It will be automatically closed in 7 days.

@github-actions github-actions bot added the stale The issue/PR was marked as stale because it has been open for too long. label Mar 17, 2023
@github-actions
Copy link

Hi everyone! This issue has been automatically closed due to inactivity.
If you think this issue is still relevant in the latest Solidity version and you have something to contribute, feel free to reopen.
However, unless the issue is a concrete proposal that can be implemented, we recommend starting a language discussion on the forum instead.

@github-actions github-actions bot added the closed due inactivity The issue/PR was automatically closed due to inactivity. label Mar 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed due inactivity The issue/PR was automatically closed due to inactivity. low effort There is not much implementation work to be done. The task is very easy or tiny. medium impact Default level of impact stale The issue/PR was marked as stale because it has been open for too long.
Projects
None yet
Development

No branches or pull requests

3 participants