Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
react-unknown-prop
See original GitHub issueWarning: Unknown props lat, lng, $hover, $getDimensions, $dimensionKey, $geoService, $onMouseAllow, $prerender on <div> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop.
After react 15, unknown props cannot be used
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:6
Top Results From Across the Web
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 >React Unknown Prop Warning - Stack Overflow
I was trying to render a DOM element with a prop but my attempt is not recognized by React as a legal DOM...
Read more >[Solved]-React Unknown Prop 'onSearch'-Reactjs
First, ref attribute accept a function as a value, which will be executed with a real dom element(opposite to virtual dom). And before...
Read more >Many routers with warning `<Component> was ... - GitHub
The 'was created with unknown prop' is a runtime error, not a compile time error, and so is unaffected by the onwarn compiler...
Read more >Unknown Prop with Framer Motion and React : r/webdev
Unknown Prop with Framer Motion and React. I'm trying to use Framer Motion to animate Reach UI's dialog component, however, I see this...
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
OK… Thanks… as a suggestion I think it would much more sense if we could pass an array of markers to google-map-react component instead of having to add a separate child inside the component. anyway… Thanks for your response and for your wonderful work!
@BesatZardosht +1 on your suggestion – I also wish we could do that. It would also be nice if this lib exposed the native google maps Marker support. Not sure if that’s something @istarkov would want but I could submit PRs