Skip to content

No labels!

There aren’t any labels for this repository quite yet.

as designed :trollface:
as designed :trollface:
automated pr
automated pr
awaiting response
awaiting response
waiting for more info from the author - will eventually close if they don't respond
based
based
non-standard/breaking change (eg. would cause issues in 3rd party code)
browser
browser
issues relating to running basedpyright in a browser environment (eg. the playground)
config
config
issues relating to config (pyproject.toml, pyrightconfig.json, LSP config or vscode extension)
documentation
documentation
Improvements or additions to documentation
duplicate
duplicate
This issue or pull request already exists
good first issue
good first issue
Good for newcomers
hacktoberfest-accepted
hacktoberfest-accepted
help wanted
help wanted
Extra attention is needed
language server
language server
LSP: code actions
LSP: code actions
LSP: completions
LSP: completions
LSP: import suggestions
LSP: import suggestions
import suggestions can show as either a code action or autocomplete suggestion
LSP: inlay hints
LSP: inlay hints
LSP: semantic highlighting
LSP: semantic highlighting
needs investigation
needs investigation
awaiting verification by a maintainer that the issue is valid
node
node
issues relating to the fact that basedpyright depends on nodejs (the nodejs-wheel pypi package)
p1
p1
performance
performance
plugin
plugin
feature specific to some third party module and therefore requires a plugin system
project
project
internal stuff relating to the repo itself (eg. ci)
pycharm parity
pycharm parity
feature that exists in pycharm but not pyright
pylance parity
pylance parity
feature that exists in pylance but not pyright / bug specific to our impl of a pylance feature
pyright parity
pyright parity
something we broke that isn't an issue in pyright
rejected upstream
rejected upstream
also a bug in pyright/pylance or feature that isn't in pyright/pylance - they refused to address it
required for [REDACTED]
required for [REDACTED]
this issue needs to be resolved before basedpyright can be fully adopted in the [REDACTED] project