-
Notifications
You must be signed in to change notification settings - Fork 47.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group warnings for unknown DOM properties #7152
Comments
If you’d like to work on this please comment in this thread so others know you’re taking it. |
I'd love to take a crack at this. |
@gm758 You got it! Let me know if you have any questions. #6800 would be a good reference for the warning we added—we just need to change it to accumulate “bad” props before emitting a single warning outside the loop. |
Fixed via #7153 |
hello, please can anyone tell me how to disable this warning? thank you! |
@kennyhk I also want to disable this warning 😢 |
You can't disable it. We don't add warnings just to make your life harder. It warns about a problematic pattern that will behave unexpectedly in the next major version. You need to fix this. If you use third party libraries and warnings come from them, you need to file issues with those libraries so they get fixed. Please read about warning and the discussion below: https://gist.github.com/jimfb/d99e0678e9da715ccf6454961ef04d1b |
We load SVG files as react components using the svg-react-loader. The SVGs come from Illustrator and have an |
I think support for xmlns has been merged just a few days ago. So it'll be out in the next version. |
Awesome to hear. Thanks. For the future, is the right solution to try to keep React's list of accepted props complete and up-to-date? |
Yes, however we should have pretty much everything from SVG and HTML. Hopefully there isn't much we missed but I fully expect new specs to come out and for us to need to handle that. |
I just ran React Bootstrap doc page on master and saw a ton of warnings from #6800:
That page is really long so maybe it’s an edge case, but at the very least I think we should group props from the same element into a single warning. For example, these warnings could become one:
The text was updated successfully, but these errors were encountered: