Hint component needs to warn when not getting scales props
See original GitHub issueRight now, if the Hint component is used but it’s not a direct child of XYPlot, a user gets the following error:
TypeError: (0 , _scalesUtils.getAttributeFunctor)(...) is not a function at Hint._getPositionInfo (http://localhost:14920/javascripts/main.js:163017:69) at Hint.render
The Hint component should make it clear what props it needs to operate correctly.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Failed prop type warning in unloaded component
Warning : Failed prop type: The prop `query` is marked as required in `OtherPage`, but its value is `undefined`. "prop-types": "^15.7", "react": ...
Read more >React with TypeScript Cheatsheet - Bits and Pieces
The ComponentPropsWithoutRef type makes it easy to create a component that's an extension of native HTML elements without having to type all ...
Read more >Best Practices for Using TypeScript and React - OneSignal
For one, you can pass any string value into the component props, even though only "primary" and "secondary" are implemented by the component....
Read more >Type '{}' is not assignable to type 'ReactNode'. #35986 - GitHub
12:35:51.922 | Type 'Component<SVGProps<SVGSVGElement>, any, any>' is ... This is getting bad, please please if anyone has suggestion on how ...
Read more >Prop physics - Valve Developer Community
Warning : If an entity has animations that will be played, ... Does not alter the physics collisions in most cases, however. Warning.png ......
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 FreeTop 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
Top GitHub Comments
I can have a look this weekend.
Regards, Alison
On Tue, Jan 17, 2017 at 11:22 PM, Andrew McNutt notifications@github.com wrote:
Hi there
I just replicated this issue successfully.
Just wondering have we added the warnings?
Cheers