Unknown Prop Warnings When Accessing Pages With Parameters
See original GitHub issueEvery time I access a route defined with parameters, the pages work perfectly but two warnings are generated. For example, I have a page called [userId].svelte
and whenever I access this page, the following warnings are generated:
<U5BuserIdu5D> was created with unknown prop 'scoped' bundle.js:7676:78
<U5BuserIdu5D> was created with unknown prop 'scopedSync' bundle.js:7676:78
Tested this in both Firefox 74 and Chrome 81, both have the same warnings. So I believe this a problem with Routify.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Many routers with warning `<Component> was created with ...
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 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 >Warning: Unknown prop `params` on <a> tag. Remove this ...
I am trying to make a profile page with react router and Warning: Unknown prop params on <a> tag. Remove this prop from...
Read more >Displaying Data with Props - From JavaScript to React - Next.js
If you run this code, React will give us a warning about a missing key prop. This is because React needs something to...
Read more >Strict mode - JavaScript - MDN Web Docs
New runtime errors · Assigning to an undeclared variable throws a ReferenceError . · Failing to assign to an object's property (e.g. it's...
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
This has been fixed and will be available in the next release.
Seems still happening on v1.5.5 - #159