-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fix: revert single template literal expression which might be intended usage #3611
Conversation
…ession template literals" This reverts commit 099b14c / jsx-eslint#3538. Fixes jsx-eslint#3607.
Codecov Report
@@ Coverage Diff @@
## master #3611 +/- ##
==========================================
- Coverage 97.62% 97.62% -0.01%
==========================================
Files 132 132
Lines 9295 9288 -7
Branches 3397 3394 -3
==========================================
- Hits 9074 9067 -7
Misses 221 221
|
4e9eb78
to
9ea0010
Compare
This has nothing to do with TS; JS also can use propTypes or runtime type checks - it's precisely as critical a use case in JS as it is in TS. Honest mistake, though - I missed this too when reviewing your initial PR. |
right, updated the description. |
698d6c7
to
f818096
Compare
Thanks, I didn't have the bandwidth over the weekend to do this in #3608 👍 |
Will this fix be released soon? |
I'm sure it will. |
This reverts #3538, while keeping the test case there for explanation and future breakage prevention.
The previous commit broke for intended type casting usage: #3607
Sorry for adding the change, did not think enough before making it, apparently this is definitely legit use case for casting other type to string, we might be able to keep this rule and limit it to string single template literal with typechecker, but just a bit overkill at this moment.