-
Notifications
You must be signed in to change notification settings - Fork 23
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
Add parameter for max depth #12
Comments
Hi, very glad you like it! It wouldn't be too hard to implement. However, depending on your needs, you might be better off using references to cap nesting. Excerpt from one of my own schemas: File product.json contains:
and types.json contains:
I display product.json in a page detailing the product API and have a second page called "Types" Note the use of "$$target". Its contents should match exactly the corresponding $ref. Hopes this helps to solve you issue. regards, |
Hi Leo, Thanks for the details, very useful! I'm getting back to you super late about this. I've been digging in the Sphinx docs to understand how to quickly add a parameter to a directive without success. I'm not sure if I'll have time to noodle with Sphinx and understand by trial and error what should be clearly explained in the docs! 😢 Ironic for a documentation platform 😄 |
Hi Arthur, It is in fact quite simple to have parameters on a directive. I can only wholeheartedly agree with your closing remark. It took a lot of time with a Please let me know if you need further pointers and I will gladly accept a pull request for this feature. |
Oops, accidently closed. |
Hello and thanks for this cool extension :)
How difficult would it be to add a parameter to choose how deep we want to read the schema?
Typically:
Thanks!
The text was updated successfully, but these errors were encountered: