Escalate pars(terms =) deprecation to error - #106
Merged
Conversation
The terms argument of pars() has warned via deprecate_warn("0.2.1")
since term 0.3.0 (September 2020). Advance it to deprecate_stop()
for the 0.4.0 release.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The
termsargument ofpars()has warned viadeprecate_warn("0.2.1")since term 0.3.0 (September 2020), well past the one-year escalation threshold.deprecate_warn()todeprecate_stop()forpars(terms =)pars_terms()dispatch branchexpect_deprecated()tests with error snapshots matching the pattern intest-deprecated.RPart of the 0.4.0 release preparation (#105).
🤖 Generated with Claude Code