Formalize Quilt mod metadata handling #83
Closed
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.
With plans to introduce support for
quilt.mod.json5
(through quilt-loader#329 and quilt-loom#36) in a limited capacity within the toolchain, formalizing how metadata should be handled has been needed. This formalizes the mandatory need to handlequilt.mod.json
and the optional need of handlingquilt.mod.json5
Considering that we are on a "down with bureaucracy" arc, I'd rather have this RFC be an explainer of things already been put in place, rather than as a precondition before we can move forward with QMJ5. I will, however, consider it as a precondition for further pushing of the format, with Quilt Template Mod waiting for a proper unveiling of the format before adopting it itself