Warning: React does not recognize the `slideCount` prop on a DOM element.
See original GitHub issueBecause of this line https://github.com/akiran/react-slick/blob/master/src/arrows.js#L35 I get errors with React 16.
What is the purpose of this? How it will help with a config like this:
nextArrow: (
<span>
<IconButton>
<FA icon={faChevronRight} />
</IconButton>
</span>
),
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:10 (1 by maintainers)
Top Results From Across the Web
React does not recognize the `currentSlide`, ` slideCount ...
js project. While using this, console shows this warnings for both 'currentSlide' and 'slideCount' prop on a DOM element. Warning: ...
Read more >React does not recognize the `currentSlide` prop on a DOM ...
Hello, I've just started with builder.io today, and have hit the first roadblock: I've started an instance of the next-js-example app from ...
Read more >React does not recognize the `currentSlide`, ` slideCount ...
Coding example for the question How to solve Warning: React does not recognize the `currentSlide`, ` slideCount` prop on a DOM element-Reactjs.
Read more >Unknown Prop Warning - React
The unknown-prop warning will fire if you attempt to render a DOM element with a prop that is not recognized by React as...
Read more >TechinPlanet - Asked By: Anonymous I am using... - Facebook
js project. While using this, console shows this warnings for both 'currentSlide' and 'slideCount' prop on a DOM element. Warning: React does not...
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
You may use this as workaround:
Why is it closed? It’s a workaround, but not the solution. Why the library is injected props directly into the function’s/component’s output?