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

pycharm plugin #27

Open
DetachHead opened this issue Jan 16, 2024 · 4 comments · May be fixed by #231
Open

pycharm plugin #27

DetachHead opened this issue Jan 16, 2024 · 4 comments · May be fixed by #231
Labels
help wanted Extra attention is needed

Comments

@DetachHead
Copy link
Owner

No description provided.

@divaltor
Copy link

Take a look on handing inlay hints based on that plugin - https://github.com/WhiteMemory99/Intellij-Python-Inlay-Params

There is good examples with built-in methods and hints with single arguments like some_method(arg) - here no inlay hints to prevent increase of cognitive load while reading a code

@DetachHead DetachHead linked a pull request Mar 31, 2024 that will close this issue
@DetachHead
Copy link
Owner Author

i had a go at this but gave up pretty quickly. documentation for intellij plugins is pretty much non-existent and their reluctance to properly support language server protocol is really annoying. what i have so far is in #231 if anybody else wants to take over

@DetachHead DetachHead added the help wanted Extra attention is needed label Mar 31, 2024
@DetachHead
Copy link
Owner Author

looks like there are now two pyright plugins that we may be able to use:

https://github.com/InSyncWithFoo/pyright-for-pycharm (pycharm community)
https://github.com/InSyncWithFoo/pyright-langserver-for-pycharm (pycharm professional)

@DetachHead
Copy link
Owner Author

DetachHead commented Jun 12, 2024

there's now an open source LSP client for intellij that actually works, we should probably use that instead so that both free & paid users get the same experience. the generic LSP plugin works with basedpyright when configured manually, but creating a decicated plugin using the developer guide is preferable, imo.

though i unfortunately don't really have the time/patience to work on it. see #231 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants