Charles Vazac

There seem to be clear use cases for leading (`*.example.com`) and trailing wildcards (`www.example.*`). Is there a use case for wildcard somewhere in the middle?

Like this? ``` const Component = ({prop = []}) => { useEffect(()=>{ // }, [prop]) return } ```

It's a great idea. This should definitely be done, and I hope to get to it. Thanks

Yes! That was always part of the plan. Let me know if you are interested in contributing.

I think both are important, but I'd prioritize 2 over 1. I had always planned to (attempt to) read more of the scope. We report on: ``` render() { return...

You are right, the plugin is naive in that it validates JSX wherever it finds it, where it should only care about JSX that is returned by `render` methods. As...

I propose using config to specify an exclude list of function names. If the JSX is seen to be an argument to a method on the excludes list, no warning/error....

Thanks for the note - you're right, this should be done. :)

@amsul absolutely, it’s a great idea.

@jugglinmike can you PTAL?