-
Notifications
You must be signed in to change notification settings - Fork 183
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
[Python APIView] docstring and annotations with *args are being mixed #8574
Comments
Additionally, since *args is included in the APIView, another * after that is not needed. It is implied that the arguments following * are kwargs. Expected APIView:
|
@tjprescott, we believe this is in the Python parser. If you find that's not true, go ahead and reassign to @chidozieononiwu |
@swathipil yes, APIView does very purposefully pull param and type info from docstrings because it does not render the docstrings. This is certainly a parser bug. |
I'm not sure why only error and messages are appearing, but are you intending to use a mix of keyword and ivar? |
Hi @tjprescott - Sorry for the late response! Didn't see this until just now. Yes, we're using both keywords and ivars. For example, the keyword |
All docstring should be using Python 3 typehints/syntax now. The Schema Registry method now looks like:
ivar with an argtype including a comma or space is still not parsed correctly. |
The [APIView] for the following method seems to be mixing docstring and annotations in the signature:
APIView:
I would expect that the APIView method signature looks entirely like the method signature and not the docstring. Should I update this method/docstring in some way or is this is an APIView bug? Thanks!
The text was updated successfully, but these errors were encountered: