Blazemod re-work preparatory restructure #39621
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
No entries deleted or edited, only file restructuring
|
You rule. Thank you for taking on Blazemod! |
ZhilkinSerg
added
[JSON]
10 tasks
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
SUMMARY: Infrastructure "Restructures blazemod file structure"Purpose of change
Simply re-organises blazemod's file structure to reflect modern vanilla standards for ease of use and better sorting, in preparation for initial re-work to begin actual changes.
Describe the solution
Added actual sub-folders to help organise json to reflect vanilla file structure, and separated out distinctive sub-categories of content groupings (i.e. normal, blob, diamond, vortex etc). This makes it far easier to address issues or modify content, and to make it easier to find what is actually changed by the rework since most of the line changes are actually this re-organisation. 5000+ was too much to skim inbetween for real changes.
Describe alternatives you've considered
Forcing other contributors to review the re-work as-is, which isn't suitable for anyone and more work than necessary when I can just do this first. The re-work shall be rebased, making is far easier to read actual changes.
Testing
No testing as nothing is changed beyond filestructure and all current issues remain as-is, to be addressed in the re-work.
Additional context
Re-work just recently went out of draft status to a full-fledged PR, which is #37497