Output squashed structs #280
Draft
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
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.
A lot of Go projects use mapstructure's
squashkeyword. Being able to usesquashwould help those projects migrate to go-jsonschema without disrupting their codebase. This PR is a quick mockup I did so that I can unblock another project.Squashing all
objects insideallOfseems like the most natural way to incorporate this feature, because all the properties of theallOfobject will become properties of the parent object. I suppose there will also be a Go compilation error if any of the property names from differentallOfobjects are the same.I believe the corresponding yaml keyword would be
inline. I'm not sure aboutjsonthough.