-
Notifications
You must be signed in to change notification settings - Fork 74
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
@zephraph => [TSLint] Rule to warn about using QueryRenderer #3108
Conversation
Thanks for the feedback! After editing the TSLint runner to avoid this severity error, I was able to get it to run, but of course the text based solution isn't going to cut it. I was in the weeds since it also seems as though the way I'm specifying an error here, doesn't seem to quite work with our TSLint version, re: the missing But I think the AST-style rule will naturally return failures that are differently structured, which might avoid that issue altogether! |
Codecov Report
@@ Coverage Diff @@
## master #3108 +/- ##
======================================
Coverage 82% 82%
======================================
Files 743 743
Lines 10883 10883
Branches 2182 2182
======================================
Hits 8933 8933
Misses 1365 1365
Partials 585 585 |
Assigning to @eessex - this adds a linter rule which fails (you can always disable the rule per line) if you use The linter did locate one such location in Tooltips that was still using Also cc @damassi I was expecting more violations but I think the sweep you did caught all of them! 👍 🙏 👏 |
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 just pulled down this branch and checked out the tooltips, everything looks good from here 👍
🚀 PR was released in v24.4.1 🚀 |
Nice @mzikherman 👍 |
Starting out with a naive rule using just string comparison...will see if an AST if needed.
This is a WIP since it's still not actually working. Getting: