News for hackers. Stuff that matters.
Re:React v15.6.0 Released by BigJono on Tuesday June 13, 2017 @10:01PM (#14550217)
Using 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.
Re:React v15.6.0 Released by jankassens on Tuesday June 13, 2017 @10:23PM (#14550286)
For 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.
Re:React v15.6.0 Released by BigJono on Wednesday June 14, 2017 @02:15AM (#14550942)
Ahhh, that makes a lot more sense!
Re:React v15.6.0 Released by cycomachead on Wednesday June 14, 2017 @01:04AM (#14550752)
I 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. :)
Re:React v15.6.0 Released by Klathmon on Wednesday June 14, 2017 @09:01AM (#14552386)
Just FYI, propTypes is moved into it's own package and WILL be removed from React-proper soon.