[ESLint] Feedback for 'exhaustive-deps' lint rule

Problem

Common Answers 💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡 We analyzed the comments on this post to provide some guidance: https://github.com/facebook/react/issues/14920#issuecomment-471070149. 💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡💡 ---- What is this This is a new ESLint rule that verifies the list of dependencies for Hooks like `useEffect` and similar, protecting against the stale closure pitfalls. For most cases it has an autofix. We'll add more documentation over the next weeks. Installation [code block] ESLint config: [code block] Simple test case to verify the rule works: [code block] The lint rule complains but my code is fine! If this new `react-hooks/exhaustive-deps` lint rule fires for you but you think your code is correct, please post in this issue. ---- BEFORE YOU POST A COMMENT Please include these three things: 1. A CodeSandbox demonstrating a minimal code example that still expresses your intent (not "foo bar" but actual UI pattern you're implementing). 2. An explanation of the steps a user does and what you expect to see on the screen. 3. An explanation of the intended API of your Hook/component. But my case is simple, I don't want to include those things! It might be simple to you — but it’s not at all simple to us. If your comment doesn't include either of them (e.g. no CodeSandbox link), we will hide your comment because it’s very hard to track the discussion otherwise. Thank you for respecting everyone’s time by including them.