uniforms: React "Unknown props" warnings
I’m not sure if this is intended or not but I get a bunch of “Unknown props” errors. Per example:
Warning: Unknown props `model`, `schema`, `validate` on <form> tag. Remove these props from the element. For details, see https://fb.me/react-unknown-prop
in form
in AutoValidatedQuickSemanticForm (created by CreateDivisionPage)
in div (created by CreateDivisionPage)
in div (created by Modal)
in div (created by Modal)
in div (created by Modal)
in Modal (created by CreateDivisionPage)
in CreateDivisionPage (created by RouterContext)
in div (created by AppLayout)
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 34 (30 by maintainers)
Commits related to this issue
- Fixed unknown props warnings from uniforms (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Fixed unknown props warnings from uniforms-bootstrap3 (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Fixed unknown props warnings from uniforms-bootstrap4 (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Fixed unknown props warnings from uniforms-semantic (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Fixed unknown props warnings from uniforms-unstyled (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Added filterDOMProps (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Removed unwanted props from uniforms-unstyled (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Removed unwanted props from uniforms-semantic (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Removed unwanted props from uniforms-bootstrap4 (#64). — committed to vazco/uniforms by radekmie 8 years ago
- Removed unwanted props from uniforms-bootstrap3 (#64). — committed to vazco/uniforms by radekmie 8 years ago
Yes, @MacRusher - that would be quite good, but some benchmarking is needed (that standard props array is big!). It’s interesting, that React doesn’t offer such function out of box.
If we could write this in a way that browsers could be able to inline cache then this wouldn’t be much of a problem, but I’m not sure at the moment if this is possible. I can only imagine that almost all React-based libraries face the same issue right now so someone must find an effective solution 😃
Seems like fixed, thanks!
I think it’s unnecessary @serkandurusoy - I’ve done it manually in
uniforms-bootstrap3- it wasn’t that hard and long.