-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fixes renaming not affecting JSX closing tags (#4093) #4096
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
Fixes renaming not affecting JSX closing tags (#4093) #4096
Conversation
//// var x = <[|MyC/**/lass|] name='hello'></[|MyClass|]>; | ||
|
||
goTo.marker(); | ||
debugger; |
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.
linter save us
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 thought I removed this 😢
@@ -30,6 +30,7 @@ tests/cases/conformance/jsx/jsxInvalidEsprimaTestSuite.tsx(11,12): error TS2304: | |||
tests/cases/conformance/jsx/jsxInvalidEsprimaTestSuite.tsx(11,16): error TS1109: Expression expected. | |||
tests/cases/conformance/jsx/jsxInvalidEsprimaTestSuite.tsx(12,2): error TS2304: Cannot find name 'a'. | |||
tests/cases/conformance/jsx/jsxInvalidEsprimaTestSuite.tsx(12,5): error TS1003: Identifier expected. | |||
tests/cases/conformance/jsx/jsxInvalidEsprimaTestSuite.tsx(12,10): error TS2304: Cannot find name 'a'. |
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.
it is unfortunate that we report the same error twice.
👍 |
Fixes renaming not affecting JSX closing tags (#4093)
Fixes #4093
We weren't wiring up the closing tags to their corresponding symbols.
This does have a side effect of causing "name not found" errors on closing tags that will always match the opening tag names. We could probably fix this if it's problematic, but would require plumbing through another boolean fairly deep into the core identifier resolution functions.