Move TOC back to top in axes documentation #11907
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I would really like to see this still go in 3.0. Please re-milestone if that's not feasible. |
jklymak
approved these changes
Aug 21, 2018
|
Should this be back ported to 2.2.x? I'm not quite sure how far back the axes changes went... |
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Aug 22, 2018
jklymak
added a commit
that referenced
this pull request
Aug 22, 2018
…907-on-v3.0.x Backport PR #11907 on branch v3.0.x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
The TOC in https://matplotlib.org/devdocs/api/axes_api.html is burried somewhere below the class doumentation.
This PR brings the TOC back to top and thus increases its usability.
As a remark: Since #11454 the scope of this page has changed from the Axes class to the Axes module. IMO the class docstring should be moved to a sub-page as well. It's the only content part of the page whereas everything else is just a collection of links. But that's something for another PR.