Refactor profession item substitution: #36520
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
Changes arrays into JSON objects as they give their "elements" names, which makes the whole structure much easier to read. This is especially visible with traits that must be there and traits that must not be there: ``` "sub": [ [ [ "ANTIWHEAT" ], [ "MEATARIAN" ], "cornbread" ], [ [ "ANTIWHEAT", "MEATARIAN" ], "meat_cooked", 0.72 ] ] ``` This defines a replacement to "cornbread" when "ANTIWHEAT" is present and "MEATARIAN" is absent. Can anybody guess that just be looking at the JSON data? ---- Removed the main "substitution" array. Instead each entry of that array is now a top level entry. ---- Added documentation.
This was referenced Jan 5, 2020
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.
SUMMARY: NoneChanges JSON arrays into objects as they give their "elements" names, which makes the whole structure much easier to read.
This is especially visible with traits that must be there and traits that must not be there:
This defines a replacement to "cornbread" when "ANTIWHEAT" is present and "MEATARIAN" is absent. Can anybody guess that just be looking at the JSON data?
Removed the main "substitution" array. Instead each entry of that array is now a top level entry.
Added documentation.