Skip to content
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

Merged
merged 5 commits into from Sep 30, 2022

Conversation

AA-Turner
Copy link
Member

Follow-up from #10807 and #6316.

Feature or Bugfix

  • Feature
  • Bugfix

cc @jakobandersen @josephmure @asmeurer

A

@asmeurer
Copy link
Contributor

I can confirm the SymPy docs still build fine with this PR.

@josephmure
Copy link

The OpenTURNS doc builds correctly with this PR. Thanks!

@jakobandersen
Copy link
Contributor

Looks good to me, except I suggest having the direction option be called notocentry, which I think provides a more direct association to the toctree directive that it in a sense modifies.

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.

@AA-Turner
Copy link
Member Author

my concern with notocentry is parsing the phrase for readers unfamilar--as the others (no index, no index entry) use smushedwords I hesitate to use e.g. no-toc-entry.

What would you prefer of either nocontentsentry or no-toc-entry?

A

@AA-Turner
Copy link
Member Author

The OpenTURNS doc builds correctly with this PR. Thanks!

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

@AA-Turner AA-Turner self-assigned this Sep 29, 2022
@jakobandersen
Copy link
Contributor

my concern with notocentry is parsing the phrase for readers unfamilar--as the others (no index, no index entry) use smushedwords I hesitate to use e.g. no-toc-entry.

What would you prefer of either nocontentsentry or no-toc-entry?

I'm not sure notocentry is that bad, but it's not too important to me. I'd rather go with the current than using dashes.

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.

@AA-Turner AA-Turner merged commit 650f63b into sphinx-doc:5.2.x Sep 30, 2022
@AA-Turner
Copy link
Member Author

Sphinx 5.2.3 has been released.

A

@josephmure
Copy link

The OpenTURNS doc builds correctly with this PR. Thanks!

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

We'll certainly test the feature, but I think we'll need a comprehensive redesign of our document to use it effectively.

marxin pushed a commit to marxin/sphinx that referenced this pull request Oct 2, 2022
- Implement `:nocontentsentry:` flag
- Use `:nocontentsentry:` in docs
- Add domain object table of contents configuration option
Bibo-Joshi added a commit to python-telegram-bot/python-telegram-bot that referenced this pull request Oct 25, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 31, 2022
@AA-Turner AA-Turner deleted the notoc branch May 12, 2023 21:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants