-
Notifications
You must be signed in to change notification settings - Fork 76
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
[jsx-curly-spacing] False positive with render props #140
Comments
There are many tslint rules which are incompatible with prettier. I suggest you use |
@adidahiya Well, it was merely a side note that I am using Prettier :) Imagine if someone would format their code this way manually and get the same error. In that case it's obviously a bug in the rule, don't you agree? |
sure, I guess so... would accept PRs to fix this false positive. typically the rules in |
I can probably take a look when I have some time.
…On Tue, Jan 30, 2018 at 8:44 AM, Adi Dahiya ***@***.***> wrote:
Reopened #140 <#140>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#140 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB2FVpF4aaiS5KkysCR2YJqA0QFl9joOks5tP0bDgaJpZM4RydY3>
.
|
Hi, |
+1, seeing this issue as well. |
Same here. |
Can we please have a release that fixes this? |
The following code is causing false positive on this rule.
tslint-react: 3.4.0
I might add that code is auto formatted by Prettier so I cannot write it differently :)
/cc @bolatovumar
The text was updated successfully, but these errors were encountered: