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
Support new mkdocstrings_handlers namespace #367
Conversation
0aad9b2
to
b8e73d7
Compare
Lets not emit deprecation warnings for our own legacy handler. Users don't care about them. |
@oprypin do you want us not to emit these deprecation warnings for the crystal handler as well? |
@pawamoy Well yes but that will just be done by making the handler use the new approach |
Indeed, it's just in case you don't plan to upgrade your handler immediately and don't want to bother your users with a deprecation warning they have no control over. Let me know. |
@@ -42,7 +40,7 @@ See the documentation for | |||
[`BaseRenderer`][mkdocstrings.handlers.base.BaseRenderer]. | |||
|
|||
Check out how the | |||
[Python handler](https://github.com/pawamoy/mkdocstrings/blob/master/src/mkdocstrings/handlers/python.py) | |||
[Python handler](https://github.com/mkdocstrings/python/blob/master/src/mkdocstrings_handlers/python) |
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.
#356 will remove this destination though
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.
Hmmm no I think it's right: this link points to the extracted Python handler, i.e. its own repository in the org, and not mkdocstrings' repo.
f9cd116
to
2b6561c
Compare
No description provided.