-
Notifications
You must be signed in to change notification settings - Fork 13
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
chore(ci): add script and workflow for auto-updating schema #286
Conversation
"strict" | ||
], | ||
"title": "Specifies the default rule set to use for type checking", | ||
"default": "basic" | ||
"default": "standard" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pyright has recently changed the default value of typeCheckingMode
from basic
to standard
. We have to decide whether we want to follow that in our settings or not. standard
triggers some new errors in LSP code base at least.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would make sense to switch to standard
since only then the default values defined in schema should actually match the reality. The issue with the LSP code base was only related to a single diagnostic reportIncompatibleMethodOverride
.
- uses: actions/checkout@v3 | ||
|
||
- name: Set up Python | ||
uses: actions/setup-python@v4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's use v5
This should help with ensuring that configuration schema is up to date.
The github workflow in theory should auto-update schema in dependabot PRs but if new pyrightconfig settings are added then it will require updating the LSP part manually.
Totally untested (especially the workflow).