-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fix double error on invalid delete of readonly property #53961
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
Conversation
This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise. |
This seems reasonable, but, it still needs some sort of test. Potentially one like those in |
@typescript-bot test this |
Heya @jakebailey, I've started to run the extended test suite on this PR at f0690e4. You can monitor the build here. |
Heya @jakebailey, I've started to run the diff-based user code test suite (tsserver) on this PR at f0690e4. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the diff-based top-repos suite on this PR at f0690e4. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the perf test suite on this PR at f0690e4. You can monitor the build here. |
Heya @jakebailey, I've started to run the tarball bundle task on this PR at f0690e4. You can monitor the build here. |
Heya @jakebailey, I've started to run the diff-based top-repos suite (tsserver) on this PR at f0690e4. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the diff-based user code test suite on this PR at f0690e4. You can monitor the build here. Update: The results are in! |
Heya @jakebailey, I've started to run the parallelized Definitely Typed test suite on this PR at f0690e4. You can monitor the build here. Update: The results are in! |
Hey @jakebailey, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running |
@jakebailey Here are the results of running the user test suite comparing There were infrastructure failures potentially unrelated to your change:
Otherwise... Everything looks good! |
@jakebailey Here are the results of running the user test suite comparing Everything looks good! |
Hey @jakebailey, it looks like the DT test run failed. Please check the log for more details. |
@jakebailey Here are the results of running the top-repos suite comparing Everything looks good! |
@typescript-bot pack this |
Heya @jakebailey, I've started to run the tarball bundle task on this PR at f0690e4. You can monitor the build here. |
Hey @jakebailey, I've packed this into an installable tgz. You can install it for testing by referencing it in your
and then running There is also a playground for this build and an npm module you can use via |
@jakebailey Here are the results of running the top-repos suite comparing Everything looks good! |
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.
Pls add test
Fixes #53082
Whenever we detect there's an error of type
The_operand_of_a_delete_operator_cannot_be_a_read_only_property
, we don't need to check for theThe_operand_of_a_delete_operator_must_be_optional
error.