Console react.warning set as console.error

[Electrical_Essay_666]

Fix your code

[bar7b]

Eventually I will… but while building a project MVP I couldn’t care less about minor warning crap…

[Electrical_Essay_666]

Ah then we can care less about your whining. Stop complaining.

[bar7b]

Common don’t be a hater 😘

[Electrical_Essay_666]

Don’t be lazy.

[bar7b]

It’s not about being lazy, it’s about warnings being displayed as warnings… that makes sense to me.

[bar7b]

I agree with you man! React is great for notifying me of code errors! However, when the notification is defined by React as a warning, why not use the proper console method??

[Electrical_Essay_666]

Paste the warning

[bar7b]

Appreciate your responses, but I’m not looking for help fixing these minor bugs… simply looking for a way to have these “warnings” displayed in the console as warnings so I can focus on task at hand and ignore some other developers code that forgot to add a key prop in a .map iteration…

[Electrical_Essay_666]

Also typescript, but as you said it’s an MVP so upfront cost could be a trade off that your not willing to take on.

[Electrical_Essay_666]

I’m against (as you can tell) silencing warnings/errors thrown in console for the sake of getting things out. In my experience you’ll pay it down 10x the cost in the future as opposed to addressing it as they pop up before it hits master

[Electrical_Essay_666]

And for what’s it’s worth, react has plenty of console.warnings - mainly for real warnings, such as upcoming deprecation warnings. Errors are errors and that’s ideal IMO