-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Make docs valid according to guides 0.3.3 #11252
Conversation
There even is a note in the official docs about it.
This silences a warning about it having no title. It also means we no longer have to work around this in the CI
I think you can replace the toc node with a container directive. As it is nothing more than just a wrapper? For the others you would indeed need an extension that adds the templates and directives to your documentation builder. If needed I can help you with that, even if it was just missing documentation on our side. |
@greg0ire @jaapio as the sectionauthor seems to be an official sphinx directive we could also add it directly to the guides: https://certik.github.io/sphinx/markup/desc.html |
Yes please 🙏 |
* 2.19.x: Fix Static Analysis folder reference (doctrine#11281) docs: recommend safer way to disable logging (doctrine#11269) Remove unused baseline entries Treat '0' as a legitimate trim char Add type field mapper documentation to the sidebar Mark document as orphan Use correction sectionauthor syntax Make docs valid according to guides 0.3.3 (doctrine#11252)
* 3.1.x: Fix Static Analysis folder reference (doctrine#11281) Remove broken assertion from DateAddFunction and DateSubFunction (doctrine#11243) Account for inversedBy being a non-falsy-string or null Improve static analysis on AttachEntityListenersListener docs: recommend safer way to disable logging (doctrine#11269) Remove unused baseline entries Treat '0' as a legitimate trim char Add type field mapper documentation to the sidebar Mark document as orphan Use correction sectionauthor syntax Remove unused trait [Documentation] Adding link to Postgres upgrade article (doctrine#11257) Validate more variadic parameters (doctrine#11261) Throw if a variadic parameter contains unexpected named arguments (doctrine#11260) Make docs valid according to guides 0.3.3 (doctrine#11252) fix: support array-type arg in QB variadic calls (doctrine#11242)
Cc @linawolf @jaapio
Here are the warnings that are left:
I suppose the next step could be to create some kind of doctrine extension for the guides that will contain the templates mentioned above, based on
?