Config doc - Write the model as JSON in jars #48702
Merged
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.
It comes with a version marker.
/cc @radcortez this is what I had in mind.
You're going to write a merger similar to
JavadocMerger
andModelMerger
but for the JSON files coming from the class loader.There's a bit too much logic in
ModelMerger
to duplicate it so it probably needs to be made more generic.I would prefer to avoid having the YAML mapper as a Dev UI dependency so we will need to extract the model and the JSON merger in a separate jar.
Happy to discuss it further with you. Note: in the end everything coming from the IDE config experiment had already been extracted, improved and merged so it should be all good for you to play with it.