Spelling mistake "separator" not "seperator" #18238
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.
Overview
This PR fixes a spelling mistake "separator" not "seperator" which inconsistent throughout the code.
Before
Sometimes variables, comments etc. use "seperator" and sometimes "separator" which could cause future bugs due to the incorrect spelling.
After
Fixed spelling and "separator" is now used consistently.
Technical Details
Have reviewed the changes and does not look like it should break anything.
Looks like the change to templates/CRM/Event/Form/ParticipantFeeSelection.tpl may actually fix a bug due to the incorrect variable name.
Where "seperator" is referenced here, https://github.com/civicrm/civicrm-core/blob/master/templates/CRM/Event/Form/ParticipantFeeSelection.tpl#L21
With the "separator" defined here, https://github.com/civicrm/civicrm-core/blob/master/templates/CRM/Price/Form/Calculate.tpl#L28
Comments
Fingers crossed unit tests catch any problems with this change.