Add support for aliases in Gregorian eras #169
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.
What are you trying to accomplish?
Part of #78. Adding support for aliases within the
eras
elements.What approach did you choose and why?
Added specific handling for
alias
nodes at that specific path.Then added the path to
validate_aliases_only_in_expected_paths
so that the list remaining alias locations gets smaller.What should reviewers focus on?
I didn't add support for aliases at
/ldml/dates/calendars/calendar/eras
, but they are only present in non-Gregorian calendars, and we don't yet export those.(I wonder if there's a nice way to change
validate_aliases_only_in_expected_paths
to also check this assertion 🤔)The impact of these changes
Three less alias locations to handle.
Testing
...
Checklist