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

Upstreaming: Customize the suppress-warnings prefix that is included in error messages #9

Open
cpovirk opened this issue Nov 11, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@cpovirk
Copy link
Collaborator

cpovirk commented Nov 11, 2020

28089b9

Obviously this is minor, and obviously it is sometimes nice to be able to suppress only a more fine-grained category. For the moment, though, I am erred on the side of making the output shorter and making it clear how to suppress. If we end up wanting to stick with that approach, we'd want to upstream.

There may be other ways around this: Maybe we'd plug in our own Messager that munges the default message.

(Note that it is not sufficient to define a single message key, nullness=%s, and then use it for all errors we report. That's because CF itself issues errors with its own keys.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants