Skip to content

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

Description

@cpovirk

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.)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions