We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
The following deprecation warning gets output with the latest mkdocstrings version:
https://github.com/mkdocstrings/autorefs/blob/40940c591e9cc557573ccd35351ca2b535ec371b/src/mkdocs_autorefs/references.py#L274-L279
I am aware that this is the legacy Python handler. Despite that, is there still interest in having this fixed?
The text was updated successfully, but these errors were encountered:
Yes, this should be fixed! Thanks for reporting.
Sorry, something went wrong.
Great!
I tried replacing this here:
python-legacy/src/mkdocstrings_handlers/python/rendering.py
Line 28 in c8aacd7
with:
return Markup("<autorefs optional-hover={path}>{brief}</autorefs>").format(path=path, brief=brief)
It fixes the warning, not sure if it's correct though. A quick comparison of some rendered output seems to be identical.
If that looks good I can create a PR.
It should be this:
return Markup("<autoref identifier={path} optional hover>{brief}</autoref>").format(path=path, brief=brief)
PR welcome! I should be able to review+merge+release tomorrow :)
refactor: Update cross-reference markup to new autorefs format
89592bd
Issue-6: #6 PR-7: #7 Co-authored-by: Timothée Mazzucotelli <dev@pawamoy.fr>
pawamoy
Successfully merging a pull request may close this issue.
Description of the bug
The following deprecation warning gets output with the latest mkdocstrings version:
https://github.com/mkdocstrings/autorefs/blob/40940c591e9cc557573ccd35351ca2b535ec371b/src/mkdocs_autorefs/references.py#L274-L279
I am aware that this is the legacy Python handler. Despite that, is there still interest in having this fixed?
The text was updated successfully, but these errors were encountered: