4 ms·
Downgrading the deprecation warnings to console.warn instead of console.error will be nice until all the third-party libraries catch up with the changes in v15.
by ljoshua 9y ago
Downgrading the deprecation warnings to console.warn instead of console.error will be nice until all the third-party libraries catch up with the changes in v15.5. It's the small things.
- BigJono 9y agoUsing console.error for warnings was silly in the first place. The solution to people ignoring warnings is to change that mindset, not to reduce the granularity of information and make everything red. I see the same thing with ESLint a lot.
- jankassens 9y agoFor a long time, console.error had a stack trace in the Chrome devtools while console.warn didn't. I believe this was the main motivation to use console.error.
- BigJono 9y agoAhhh, that makes a lot more sense!
- cycomachead 9y agoI ran into this a lot with propType validations, which don't seem to be changing. But I'm in the camp that are "warning" should be displayed as a warning, so this is a welcome change. :)
- Klathmon 9y agoJust FYI, propTypes is moved into it's own package and WILL be removed from React-proper soon.