Add support for finer grained censoring of user defined warnings #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds a
--censor-user-defined-warnings=WARNING
flag to ignore Warn constraints whose message containsWARNING
. It can be specified multiple times to ignore different warnings.For instance, given this spago.dhall:
the following program:
yields those warnings when compiled with
npx spago build
:Compiling with
npx spago build -u "--censor-user-defined-warnings=\"'foo' is deprecated\""
yields:Compiling with
npx spago build -u "--strict --censor-user-defined-warnings=\"'foo' is deprecated\" --censor-user-defined-warnings=\"bar\""
yields no warnings.This doesn’t alter the behaviour of the existing
--censor-warnings
and--censor-codes=UserDefinedWarning
flags:psa --censor-warnings --censor-user-defined-warnings=WARNING
still censor all warnings andpsa --censor-codes=UserDefinedWarning --censor-user-defined-warnings=WARNING
still censor all user defined warnings.purescript-psa-utils
has been updated with the latest Argonaut libraries, which introduces typed errors, on master so I also had to make three small unrelated changes.