We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This section on the README.md –
_
Schema Files Note that schema stored here is just a cache for helping development. Developers should make sure download latest schema from http://github.com/Juniper/contrail-api-client JSON version stored in public/schema.json
Schema Files
Note that schema stored here is just a cache for helping development. Developers should make sure download latest schema from http://github.com/Juniper/contrail-api-client
JSON version stored in public/schema.json
If the intent is that the user always uses the latest schema managed under a different repository, why don’t you just use a git submodule for this?
The text was updated successfully, but these errors were encountered:
Contrail repos are under migration now. so I would like to use git subtree once main repo get ready
git sub tree: https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree
Sorry, something went wrong.
I'm not opinionated on either option, other than it should be done rather than asking users to copy from a different repo.
kk let's keep open this issue until this issue get fixed.
No branches or pull requests
This section on the README.md –
_
_
If the intent is that the user always uses the latest schema managed under a different repository, why don’t you just use a git submodule for this?
The text was updated successfully, but these errors were encountered: