Prop warnings from dependencies
See original GitHub issueDescribe the bug
React v 15.8 has become very noisy with errors of the form “Unknown event handler property onVisibilityChange
. It will be ignored”.
That’s all very well but in some cases it is our dependencies that are doing this. Sadly this problem comes through to users of Storybook.
Not quite sure if there is some workaround here (apart from PR-ing our dependencies of course). Let’s collect a list here:
react-popper-tooltip
(onVisibilityChange
toTooltipTrigger
)
To Reproduce Run any the beta storybook (official storybook or a user storybook)
Expected behavior No warnings
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Warning for 'exhaustive-deps' keeps asking for the full 'props ...
The example 1 gives me the following warning in CodeSandbox environment: React Hook useEffect has a missing dependency: 'props.myProp'.
Read more >Understanding the React exhaustive-deps linting warning
The first exhaustive deps warning we got was because a single primitive variable was missing in the dependency array.
Read more >React.js Passing setState as prop causes a warning about ...
The issue is that I get a warning saying I need to use props in my dependency array, however, I do not want...
Read more >Command-Line Interface - Gradle User Manual
By default, Gradle won't display all warnings (e.g. deprecation warnings). Instead, Gradle will collect them and render a summary at the end of...
Read more >PackageReference in project files - NuGet - Microsoft Learn
Using PackageReference for a project with no package dependencies ... NuGet observes the following warning properties:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Actually totally false accusations on
react-popper-tooltip
, it was us, also fixed in above PRHey @web-padawan,
The middle one is. The other two are issues that still need to be resolved (I think the last one has been, see #5602). I’ll sort out the first.