You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, having a module type hint translates into the documentation into giving the url of the module source on my machine.
This should be fixed asap.
The text was updated successfully, but these errors were encountered:
I tried to run apidoc more cleanly, with a recent interface. It is currently failing spectacularly. I'm not sure but I suspect it is a problem of compatibility of our way of using type hints and the apidoc code.
I have opened an issue on their github here
Idenitfied a problem where autoapi crashes when working with a type imported directly from a package.
Instead I make a reference to the type directly through the imported module's namespace, and it works fine. This only leads to a couple of unusual lines in the imports, but acceptable. We may revisit when the issue is fixed on the side of autoapi
At the moment, having a
module
type hint translates into the documentation into giving the url of the module source on my machine.This should be fixed asap.
The text was updated successfully, but these errors were encountered: