Suggest recode_values() in the recode() docs
#7734
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
hadley
approved these changes
Oct 10, 2025
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.
recode_values()andreplace_values()are a much more holistic replacement forrecode()thancase_match()!recode()was trying to be both a "full recode" and "partial replacement" function, which resulted in weird behavior that was pretty easy to run into. Evencase_match()wasn't a good replacement, because to do a "partial replacement" the right way you needed the.defaultand.ptypearguments.recode(x, !!!lookup)wasn't supported bycase_match(), making migration difficult. We can now use thefromandtoarguments, which also support more than just character values as well.