Split api/Element.json
#26492
Closed
Split api/Element.json
#26492
Conversation
This file contains hidden or 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
github-actions
bot
added
data:api
caugner
added a commit
that referenced
this pull request
Apr 11, 2025
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@Elchi3 @queengooborg Do you have concerns with splitting up these large files? (cc @ddbeck) |
github-actions
bot
added
the
merge conflicts 🚧
|
This pull request has merge conflicts that must be resolved before it can be merged. |
|
Closing as discussed in today's BCD meeting. |
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
Splits up
api/Element.json(over 11k lines), such that all subfeatures are inapi/Element/<subfeature>.json.Test results and supporting details
Done by running
npm run split -- api/Element.jsonin thesplit-scriptbranch.Related issues