Add warning gem to development dependencies #42
Merged
Conversation
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
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 includes changes to improve the handling of warnings and deprecations in the project. The most important changes include setting an environment variable for Ruby options, adding a new dependency for handling warnings, and configuring the warning processing behavior in the test suite.
Enhancements to warnings and deprecations handling:
.github/workflows/ci.yml: Added theRUBYOPTenvironment variable to enable deprecation warnings.spec/spec_helper.rb: Added thewarninggem and configured it to raise exceptions on warnings.trace_location.gemspec: Addedwarningas a development dependency.