You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for trying out an alpha build and providing your feedback!
I actually think that it's not great that we use the fully qualified domain name in headings for anything other than modules. It creates too much redundancy, other than maybe in projects where there's very little nesting (like with pandas).
So I instead propose that we use the name of the entity as the heading, rather than the fully qualified name.
As for "pre" tags, I've always been on the fence about whether I like the look of the monospaced headings, both on the page and in the side bar. The links that it outputs aren't really useful and, as you say, it comes at the cost of not wrapping. So I'd be up for removing that too.
So you are even suggesting to change the default template ?
I'm happy with that but I think I should wait for #399 to be merged to avoid polluting too much an already complex PR.
In the meantime could you advise on the process I should follow to update the templates ?
I'll make an edition to the documentation.
I'm using sphinx-autoapi to build my documentation and specifically the release 3.1.0a3 to build every method of my classes on a specific page: https://geetools.readthedocs.io/en/latest/autoapi/index.html
The problem is that now the titles are way too long to be displayed on a single line and "pre" tags in my html build don't wrap as normal text.
I would like to display them as pure h1 as in the pandas documentation to ensure they behave as normal text.
I assume I need to modify a template but I didn't understand which one and where to store it when reading your documentation
The text was updated successfully, but these errors were encountered: