-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prune the data before exporting to YAML ✂️ 📉 #86
Merged
Merged
Conversation
This file contains 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
movermeyer
force-pushed
the
mo.prune_yaml_files
branch
from
November 16, 2021 15:08
9dc164f
to
e9c1ae3
Compare
movermeyer
commented
Nov 16, 2021
Comment on lines
-27
to
-28
- Only export plural keys for currencies that have pluralization data, [80](https://github.com/ruby-i18n/ruby-cldr/pull/80) | ||
- Sort the exported data by key, [82](https://github.com/ruby-i18n/ruby-cldr/pull/82) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just adding the missing #
in the link text
movermeyer
changed the title
Prune the data before exporting to YAML
Prune the data before exporting to YAML 📉
Nov 16, 2021
movermeyer
changed the title
Prune the data before exporting to YAML 📉
Prune the data before exporting to YAML ✂️ 📉
Nov 16, 2021
Korri
reviewed
Nov 16, 2021
movermeyer
force-pushed
the
mo.prune_yaml_files
branch
3 times, most recently
from
November 16, 2021 15:47
7ab4802
to
c043130
Compare
trishrempel
reviewed
Nov 16, 2021
movermeyer
force-pushed
the
mo.prune_yaml_files
branch
from
November 16, 2021 17:09
c043130
to
2b36f7a
Compare
trishrempel
reviewed
Nov 16, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't explicitly approve, but looks good to me! 👍
Korri
approved these changes
Nov 17, 2021
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.
What are you trying to accomplish?
Fixes #85
There are many places in the code that are using a
select(...).inject({})
pattern for producing data, which produces emptyHash
's whenever there is no data in the XML.What approach did you choose and why?
Prune the empty hashes recursively before outputting to YAML.
Since
yaml.rb
will already not outputif data.empty?
, it will not output a file in cases where there is no relevant data to output (i.e., the file is entirely empty hashes).What should reviewers focus on?
Could there be any place in the code where an empty Hash is appropriate to output?
I contend that there is not.
The impact of these changes
Thousands of fewer files are output, and those that are output are smaller since they no longer contain empty nested key structures.
.yml
filesTesting
You can test it yourself: