Fixes rubocop violation Performance/StringReplacement #1039
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.
Summary
Fixes rubocop violation Performance/StringReplacement
Details
Changes to stop using
.gsub()
to do character replacements, but use,tr()
instead. Also, when.gsub()
was used to delete a character, we are now using.delete()
.Motivation and Context
This change makes sure our code is compliant with the ruboxop
Performance/StringReplacemenet
ruleRefs #1021
How Has This Been Tested?
I have run all the tests with
bundle exec rake
and everything is green. Rubocop is happy too.Screenshots (if appropriate):
N/A
Types of changes
Checklist: