-
Notifications
You must be signed in to change notification settings - Fork 90
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
Render TOC in nested pages #261
Conversation
I suggest...
I can take care of #213, but please let me know if you have intent to do it. |
9c3293a
to
ee6c995
Compare
Thanks for the suggestions and apologies for bundling everything (the changes seemed rather small). I changed the history to reflect the individual changes accordingly.
There's a large number of other nested files (40+) that are not currently tested. Although I agree that #213 must be fixed, I don't see why this PR should be blocked until then. I can add the generated nested expect files if that helps for now. I'm currently working on other PRs, so feel free to work on #213. |
It is possible to test this now! I'll add the generated files later today. |
…n to nested test case.
3df7680
to
409e0d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aantron I think this can be merged now, unless you have any objections/suggestions. |
Yes. If the changes are trivial, I'll just make them. |
Currently the table of contents is only rendered for top-level modules. This PR implements the rendering for all nested items (modules, module types, classes, functors and functor parameters) and makes some other minor adjustments.
Full list of changes
doc
CSS class from class items, to be consistent with other nested items (diff).ul
(and not as adl
).