**Packages**
* `"react": "^16.13.1"`
* `"eslint-plugin-react-hooks": "^4.0.8"`

The issue #18819 still happens with `eslint-plugin-react-hooks@4.0.8`.

Using the example code from the other issue gives the following errors:

![image](https://user-images.githubusercontent.com/37122343/90794940-59d9a980-e305-11ea-9ec0-98f69b41c280.png)

![image](https://user-images.githubusercontent.com/37122343/90795019-770e7800-e305-11ea-92b8-b64407b0b22c.png)


useCustomHook();
          }
          return <button>{props.children}</button>;
        });
      `,
      errors: [conditionalError('useCustomHook')],
    },
    {
      code: `
        // This is invalid because "use"-prefixed functions used in named
        // functions are assumed to be hooks.
        React.unknownFunction(function notAComponent(foo, bar) {
          useProbablyAHook(bar)
        });
      `,
      errors: [functionError('useProbablyAHook', 'notAComponent')],
    },
    {
      code: `
        // Invalid because it's dangerous.
        // Normally, this would crash, but not if you use inline requires.
        // This *must* be invalid.
        // It's expected to have some false positives, but arguably
        // they are confusing anyway due to the use*() convention
        // already being associated with Hooks.
        useState();
        if (foo) {
          const foo = React.useCallback(() => {});
        }
        useCustomHook();