Use yaml for package data instead of json #569
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
uncenter
commented
Sep 27, 2023
|
You can see the changes made in this PR by cloning this branch locally and running |
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.
This is a continuation of sorts of #567 - I noticed a lot of issues in the
md-variables.jsonfile probably arose due to how difficult it was to edit arrays of strings! YAML isn't everyone's favorite, but I think it really shines here with the multiline strings. This PR converts themd-variables.jsonfile to YAML, including my typo fixes from #567, and updates thescripts/generate-readmes.jsscript accordingly to parse the YAML.