refactor: missed lint message .to_string() change to .to_owned() - #3749
Merged
hippietrail merged 1 commit intoJul 2, 2026
Merged
Conversation
Continues on from what was missed in Automattic#3569
hippietrail
enabled auto-merge
July 2, 2026 10:11
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.
Issues
Continues on from what was missed in #3569
Description
Back in #3569 I thought I changed all the
messagefields ofLints that were using.to_string()to standardize on.to_owned()after looking into why both were used and finding reasons that.to_owned()was probably the better one after all, despite my using.to_string()in most of my linters.Before searching the repo I expected only the skeleton linters were still using
.to_string()but there was a lot I was missing!How Has This Been Tested?
cargo testAI Disclosure
Checklist