`jsx-no-leaked-render` should only complain if there is a certian leaked render

[AhmedBaset]

`jsx-no-leaked-render` should only complain if there is a certian leaked render

[ljharb]

Sounds like a great enhancement. It should be behind an option (perhaps the option disables this behavior so that the default is friendlier?). It should only kick in when the AST has type info and it knows for sure it’s not a number or string or bigint.

[AhmedBaset]

It should only kick in when the AST has type info and it knows for sure it’s not a number or string or bigint.

Does the plugin use TS type parsing at the moment?

[ljharb]

If the TS parser is used, and attaches type info to the AST, we can (and often do) use it.

[yusufkinatas]

I think this issue means making the rule recognize all 3 variables below are essentially boolean values.

I guess similar to how VSCode tells the type of a variable when hovered?

I would love to help improving this rule, but pretty new to this repository. Do we have any examples of similar TS type parsing?

[ljharb]

@yusufkinatas we don't typically have type-specific stuff, so off the top of my head i'm not sure where to look. however, you could always do the brute force approach and add some test cases and some console.logs, and see what type info is available on the AST nodes :-)