Actually deactivate warning 4.#3
Merged
fhammerschmidt merged 1 commit intorescript-react-native:masterfrom Apr 20, 2020
Merged
Conversation
cknitt
approved these changes
Apr 20, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I installed this library recently and got an annoying warning no. 4. This does not work in our setup, where we lift all warnings to errors in CI.
I think the behavior of "-warn-error @a-4" is a bit confusing here, because it promotes the warning 4 (which is disabled by default) to an error with @A and then downgrades it again to a warning.