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
When developing the library, I tested the major editors (Neovim, VSCode, PyCharm) to ensure that autocomplete worked. However, as commented here, some development environments don't pick the signatures of extensions correctly. Perhaps this is related.
Concrete steps to be made:
add __text_signature__ to methods in Rust extension
eliminate Disambiguation alias so the literals are shown directly
The text was updated successfully, but these errors were encountered:
I have complained prematurely: PyCharm does show the type hint only when entering the parameter.
Maybe the behavior was changed or it was always this way but I somehow missed it.
So imho the disambiguation is fine.
The next release should significantly improve autocomplete for IDEs at least. There are more and better docstrings, and they link to the docs where needed
When developing the library, I tested the major editors (Neovim, VSCode, PyCharm) to ensure that autocomplete worked. However, as commented here, some development environments don't pick the signatures of extensions correctly. Perhaps this is related.
Concrete steps to be made:
__text_signature__
to methods in Rust extensionDisambiguation
alias so the literals are shown directlyThe text was updated successfully, but these errors were encountered: