Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
-
@asgs Source control maybe? I don't reorder imports for that reason, but I wouldn't start a fight over it.
Also if they're incorrectly using the global scope it could also be an issue. Polyfills should also always come first, so if those get reordered it could be dangerous, but that depends on how they're implemented
lols, just salute
when eslint has had enough of your shit
Code: *Exists*
TSLint Nibbas:
Me to team: eslint-plugin-import is tripling the time it takes to lint our project (literally adding minutes to the linting process). Do we really need it?
Boss: what does it do?
Me: ensures import paths are correct; reorders imports; ...
Teammate: imports should NEVER be reordered!
*cue debate about reordering imports that is still raging - my question is never answered*
rant
eslint
debate