-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Finer grained control over domain ToC entries #10886
Conversation
I can confirm the SymPy docs still build fine with this PR. |
The OpenTURNS doc builds correctly with this PR. Thanks! |
Looks good to me, except I suggest having the direction option be called Somehow the changelog should gain an "incompatible changes" entry, where the new configuration option is mentioned to restore the old behaviour, but I guess it's not feasible to retroactively change the 5.2 entries. Thanks for the quick response. |
my concern with What would you prefer of either A |
Thank you for testing. I would ask that you consider for a little while keeping the ToC entries enabled in your documentation -- I have found it very useful in reference documentation to be able to jump directly to the object I want, and your readers may do too. I admit to significant bias here, though, as I implemented the feature, and it would be nice for it to be used rather than disabled. A |
I'm not sure I think it's a great feature to have the automatic toc entries. The point of the option is that users can enable them when they are ready, and still get the benefit of newer Sphinx versions in general. |
Sphinx 5.2.3 has been released. A |
We'll certainly test the feature, but I think we'll need a comprehensive redesign of our document to use it effectively. |
- Implement `:nocontentsentry:` flag - Use `:nocontentsentry:` in docs - Add domain object table of contents configuration option
Follow-up from #10807 and #6316.
Feature or Bugfix
cc @jakobandersen @josephmure @asmeurer
A