Add a doc.go file so the compose/schema/data directory can be vendore… #1169
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
…d in another project, without being pruned. Signed-off-by: Silvin Lubecki <silvin.lubecki@docker.com>
|
Cloned from #1162 which I couldn't reopen. Finally @thaJeztah, I really want/need the json files 😅 |
|
|
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.
- What I did
Compose JSON schemas are stored in directory, without any go code in it, so it cannot be vendored if the pruning is enabled.
- How I did it
I simply added a doc.go file...
- How to verify it
=> Schemas are still there!
- A picture of a cute animal (not mandatory but encouraged)
