-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
feat: remove conditional unstable type-checking #21825
feat: remove conditional unstable type-checking #21825
Conversation
I wonder if we should remove all the code related to "unstable" from the LSP. Thoughts on that? |
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.
LGTM
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.
LGTM
…enoland#21991) It appears I missed this in denoland#21825.
Does this change completely prevent the ability to type-check code that is intended to use only stable features (in order to detect invalid unstable references prior to runtime), or is there some alternative mechanism to do so? |
That's correct. Now all APIs are unconditionally type-checked. |
This commit removes conditional type-checking of unstable APIs.
Before this commit
deno check
(or any other type-checking command and the LSP)would error out if there was an unstable API in the code, but not
--unstable
flagprovided.
This situation hinders DX and makes it harder to configure Deno. Failing during
runtime unless
--unstable
flag is provided is enough in this case.