|
|
|
|
|
|
by mynameisvlad
1271 days ago
|
|
|
That still doesn’t change my comment. It used to explicitly be a thing you must not do for years, it’s weird to go straight 180 on something you actively warn developers not to do. If it wasn’t well documented in the past, then that’s reasonable, but actively spitting out console warnings and explicit documentation warning against it is just going to mean that anyone who isn’t new to react is going to be extremely weary about it. |
|
|