Philipp Kursawe

@JWWon your typings are missing the `ref` prop. I tried it with ```ts ref: RefObject; ``` but it compains when using `useRef` as a ref. 

Thanks for the PR. Maybe @xiaoyann could merge?

how about this rule only applies when using together with && and not as explicit return values: `obj && obj.foo && callSomeFunction(obj.foo)` or JSX (where I wanted to use such...

> @vladimir-poleh Thanks, indeed ! The stacktrace wasn't straightforward, I ended up installing gmvault in a custom docker image with python 2.7. May I ask you to share the dockerfile...

A new option would be good. Props should not be validated by default. Also the fix should not result to `null` in ternary operator but to `undefined` or it should...

re: `null` thats correct for render returns but not for props. I was unclear. I meant for props fixes it should use undefined and not null.

Given those 2 components: ```tsx function Button({ type = "primary"}) { ... } function Parent({ count: number }) { return } ``` the linting rule would change this: ```diff -return...

You see the problem with null in that case though?

> Yes, but a present undefined prop isn't the same thing as an absent prop either. Like for the JSX compiler? Would you mind to explain?

I constantly run into this problem during mentoring (beginners and seasoned devs). And I do not agree that it is called "mirroring". It's initialisation and there a perfect reasonable use...