Rename m
to mount
, but keep signature
#1226
Merged
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.
Background and context
mount
, and had a signature of:mount MyComponent.new(name: "Test")
mount
->m
occurred, which also changed the method signature to:m MyComponent, name: "Test"
m
tomount
, but keep signature #1221 opened after several issue discussions about which direction to take, deciding to revert the rename but maintain the new signature.Purpose
This PR renames
m
->mount
, retains the method signature as-is, and removes the old signature completely.Closes #1221
Description
I believe I caught everything necessary. I used the regular expressions
\bm[\s(]+[A-Z]
to locate the items that needed to be changed. The only things I'd call out that need explicit review:m
,mount
with the old signature, or do we just revert tomount
with the new signature to get any confusion sorted during the next version bump?UPGRADE.md
file was allowed, but it seemed prudent to let anyone migrating from 0.22 -> 0.23 know that they don't really need to renamemount
->m
.Checklist
crystal tool format spec src
./script/setup
./script/test