Skip to content
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

Improved autocomplete #176

Closed
2 tasks done
ariebovenberg opened this issue Oct 16, 2024 · 4 comments
Closed
2 tasks done

Improved autocomplete #176

ariebovenberg opened this issue Oct 16, 2024 · 4 comments
Labels
discussion Discussion is needed before proceeding in development Has been addressed but not released yet

Comments

@ariebovenberg
Copy link
Owner

ariebovenberg commented Oct 16, 2024

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
@ariebovenberg ariebovenberg added the discussion Discussion is needed before proceeding label Oct 16, 2024
@spacemanspiff2007
Copy link

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.

grafik
grafik

@ariebovenberg
Copy link
Owner Author

Good to hear PyCharm doesn't suffer from this issue. To be safe though, I'll still remove the alias since other editors/checkers may not.

@ariebovenberg
Copy link
Owner Author

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

@ariebovenberg ariebovenberg added the in development Has been addressed but not released yet label Oct 31, 2024
@ariebovenberg
Copy link
Owner Author

text signature has been properly configured in the latest release. One lingering issue is docstrings in the extension, which will get a separate issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Discussion is needed before proceeding in development Has been addressed but not released yet
Projects
None yet
Development

No branches or pull requests

2 participants