-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Docson dependency & reference resolution #36
Comments
(1) Maybe it should probably be part of the the data-standard repository, as in theory someone could take the content and use it with a different theme, and in those cases, docson would be required? (I think) I don't know tho. |
Thanks :) Reasoning for having this in the standard makes sense to me :) Thanks for looking into (3). |
Ok, so I've made a version of docson with all the latest code, and our 2 small patches on top of it. To try it, Change to the docson directory and run:
NOTE; if you commit at this point you'll also commit this update for everyone. You probably don't want to do that! To put this back how it was before, run:
Anyway, give that a good test, let me know if it solves your problem. (For me I can't compile the site at all at the moment.) |
Just tested and that commit was working nicely in a fresh rebuild of the docs :) |
Cool - I'm not sure what branch to go for but if you want to commit this on a branch of the data standard, simply run the "git checkout 320619...." command in the "docson" folder and then go up to the "data-standard" folder and git commit as normal. It should show a change in "docs/_static/docson" |
(I'm not sure if this best belongs as part of the theme, or as part of the docs repo: but putting here to avoid it getting lost amongst standard issues)
We use docson as a schema viewer.
At present this is a sub-module in the docs /_static/ folder.
The version we use does not have this fix in which we need: https://github.com/lbovet/docson/pull/41/files to handle json pointers in external files
There are three things we need to address:
The text was updated successfully, but these errors were encountered: