inNavbar, addonType... error
See original GitHub issuehelp me
Warning: React does not recognize the `inNavbar` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `innavbar` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
Warning: React does not recognize the `addonType` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `addontype` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
reactstrap version 5.0.0-alpha.4 bootstrap version 4.0.0-beta.3
Issue Analytics
- State:
- Created 6 years ago
- Reactions:9
- Comments:9 (1 by maintainers)
Top Results From Across the Web
React Navbar Error: Element type is invalid: - Stack Overflow
I'm trying to create a react-bootstrap navbar with a toggling element(which will be a chart.js element but is currently just a placeholder image ......
Read more >reactstrap - UNPKG
n return;\n }\n var err = new Error(\n 'Calling PropTypes validators ... 'down',\n nav: false,\n active: false,\n addonType: false,\n inNavbar: false,\n ...
Read more >reactstrap DropdownItem JavaScript Examples - ProgramCreek.com
This page shows JavaScript code examples of reactstrap DropdownItem.
Read more >Developers - inNavbar, addonType... error - - Bountysource
Warning: React does not recognize the `inNavbar` prop on a DOM element. If you intentionally want it to appear in the DOM as...
Read more >toolkit/components/telemetry/app/TelemetryEnvironment.jsm ...
Bug 1795467 - Include some targeting in background update Glean ... @return a string with the locale or null on failure. ... addonType...
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
I resolved this problem as follows.
The following workaround works for me: