Prevent treating warnings as errors from conflicting in consuming packages #71
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.
Per #70, turning on
.treatAllWarnings(as: .error)in a library causes errors for library consumers since Swift Package Manager suppresses warnings in package dependencies.We're still enforcing warnings as errors in CI, so we aren't going to introduce warnings into the repo. Unfortunate design decision within SPM, but here we are.