InSync

@angelozerr They are all as expected: ```text [Trace - 18:56:33] Received request 'workspace/configuration - (1)' Params: { "items": [ { "scopeUri": "file:///~/project", "section": "python" } ] } [Trace - 18:56:33]...

@angelozerr PR merged, gist updated.

None of them work. The easiest to test with would be `pythonPath`; it causes imports from third-party packages to be reported as unresolvable even if they are installed within the...

@angelozerr I can say with absolute certainty that such extra settings are of no consequences; Pyright simply ignores them. And yes, I send the same settings from the native client...

This is [expected](https://insyncwithfoo.github.io/pyright-for-pycharm/configurations/executables/#configuration-files). Pyright's LSP mode does not support explicit explicit configuration file. See [this discussion](https://github.com/microsoft/pyright/discussions/7650). You can file an enhancement request for Pyright, though.

That wouldn't work, since LSP mode uses [workspace folders](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_workspaceFolders) and not the working directory. You can try [the build](https://github.com/InSyncWithFoo/pyright-for-pycharm/actions/runs/10570018222) out yourself to verify this. LSP4IJ, which is the client this...

@dependabot recreate

LSP4IJ as a running mode will not be removed, since people are still using it and it still supports more than the native client does. This is just about changing...

There used to be such a feature prior to #79. These were what I thought back then: * The user would need to input the path manually (terrible UX, I...

Another possible narrowing pattern: ```python a: LiteralString if a == "foo": reveal_type(a) # revealed: Literal["foo"] ```