-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Re-enable displaying type errors in pyrefly #5046
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
base: master
Are you sure you want to change the base?
Conversation
|
cc @oliverralbertini @connernilsen if either of you are interested |
connernilsen
left a comment
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.
Thanks for doing this @sivel! Left two comments around documentation clarity, but otherwise looks great!
oliverralbertini
left a comment
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.
Thanks for adding this.
|
@hsanson I've addressed the linting issue that CI uncovered. I think the tests can be kicked off again. |
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.
Looks good, but there are some linter errors that need fixing.
In
pyrefly0.31.1a new configurationpython.pyrefly.displayTypeErrorswas added, changing the previous default behavior.This PR adds the appropriate LSP configuration to restore the behavior for the ale pyrefly linter, including a new
python_pyrefly_configoption to allow further configuration of the LSP.