insyncwithfoo / pyright-for-pycharm Goto Github PK

What happened?

I've downloaded and installed plugin version 0.1.0-mvp.5 into intelliJ IDEA 2023.3.5

When editing the global or local settings, they simply won't save. When I add the path to the executable or config file, I see the 'file found' tick, but the 'Apply' button never enables, and click 'OK' simply closes the Settings dialog, but the values are not saved/

Relevant log output or stack trace

No response

Steps to reproduce

1. Download Pyright-0.1.0-mvp.5.zip
2. Install the plugin from DIsk
3. Try to configure the Global or Project settings
4. Close the settings dialog
5. Reopen and see that the configuration values did not persist

Operating system

macOS

Feature or enhancement

On Linux:

• Virtual environment executables directory: venv/bin/
• Extension: None

On Windows:

• Virtual environment executables directory: venv\Scripts\
• Extension: .exe

It would be nice if project configurations can be shared among colleagues who use different OSes.

Proposed solution

A new configuration should be added as a checkbox in the project-level panel. The path resolving algorithm also needs modifications:

1. If there is a file/directory/symlink/etc. at the precise path given, use that.
2. Otherwise, if the topmost fragment has no extension, append the corresponding extension by OS and redo step 1.

The hard part of this is to make the UI hint react when the checkbox changes its state.

Things to do:

• Make sure release.yaml works.
• Edit the docs so that both plugins are reflected.

Either the link is broken or the repository is not public.

The LSP version is the one I'm most interested in testing/helping with :)

What happened?

The plugin is constantly performing save, and too fast. For who use formatter triggered on save it becomes hard to work.

Is it possible to avoid that?

I totally understand if this is the only way that the plugin can work.

Relevant log output or stack trace

No response

Steps to reproduce

Use some formatter on save.

Operating System

None

From this review:

The one thing I find hard with this plugin is the way in which these errors are reported. Instead of the nice, yellowish warnings you usually see, they will be reported as full on errors (with red underlines).

By default:

CLI previously had lower levels, but it was changed to match LSP. I still think this is a sane default and thus it will likely not change.

However, considering that many Python users have come to it due to its dynamicity, they probably don't want to see type errors highlighted as bona fide errors.

Maybe it expired? I think I have the tooling setup to build this on my own but wanted to check and see if you have a release zip handy?

See sister #15.

This is presumably due to the UI overhaul in 6e4f8c7, which introduced bind*() calls:

makeGlobalExecutableInput {
    // ...
    bindText(state::globalExecutable)
}

row(NO_LABEL) {
    makeAlwaysUseGlobalInput().bindSelected(state::alwaysUseGlobal)
}

Apparently, this behaviour is "documented":

The property is applied only when DialogPanel.apply() is invoked.

— Cell.bind | Kotlin UI DSL Version 2

I'm not sure what that means exactly (am I supposed to call that method or what?) but I'm working on a fix. v0.1.0-mvp.5 is hereby yanked and should not be used.