2 ms·
Unfortunately we use tslint so we'd have to add eslint just for this. > It’s also worth noting that most class components people write don’t handle all prop up
by ng12 8y ago
Unfortunately we use tslint so we'd have to add eslint just for this.
> It’s also worth noting that most class components people write don’t handle all prop updates correctly
I'm very guilty of this however I'm usually being intentionally lazy and assuming that a certain prop won't ever update. With useEffect it usually happens by mistake.
- frio 8y ago> Unfortunately we use tslint so we'd have to add eslint just for this. This won't be a problem forever (https://medium.com/palantir/tslint-in-2019-1a144c2317a9 https://medium.com/palantir/tslint-in-2019-1a144c2317a9) :).