I’ve worked at several places that didn’t have formatters when I started. they did by the time I left. you can incrementally adopt them and if it’s automated most people at worst don’t care. advocate for things you want
reassignment and hoisting are the significant ones. behavior around this does just seem more intuitive than otherwise when it comes up, so I think telling especially new devs to use const arrow fn everywhere but classes is a reasonable rule
hate to break it to you but it behaves like a variable either way. function just behaves closer to a var variable. const fns are less like variables since no assignment. intellisense/devtools all show them just fine. it really is just a minor aesthetic difference on the definition
I’ve worked at several places that didn’t have formatters when I started. they did by the time I left. you can incrementally adopt them and if it’s automated most people at worst don’t care. advocate for things you want
We use formatters, I just disagree with our current conventions (nitpicky, I know).
hate to break it to you but it behaves like a variable either way. function just behaves closer to a var variable. const fns are less like variables since no assignment. intellisense/devtools all show them just fine. it really is just a minor aesthetic difference on the definition
To me it’s about readability and declaring everything as const goes against that.
What benefits does it have? Using this in arrow functions is still valid it’s just that they will use parent scope to resolve it. You saying it doesn’t have this or arguments doesn’t convey any benefits (nor real drawbacks) to me. Hence the convention feels useless at best.
I’ve worked at several places that didn’t have formatters when I started. they did by the time I left. you can incrementally adopt them and if it’s automated most people at worst don’t care. advocate for things you want
reassignment and hoisting are the significant ones. behavior around
thisdoes just seem more intuitive than otherwise when it comes up, so I think telling especially new devs to use const arrow fn everywhere but classes is a reasonable rulehate to break it to you but it behaves like a variable either way.
functionjust behaves closer to avarvariable.constfns are less like variables since no assignment. intellisense/devtools all show them just fine. it really is just a minor aesthetic difference on the definitionWe use formatters, I just disagree with our current conventions (nitpicky, I know).
To me it’s about readability and declaring everything as
constgoes against that.What benefits does it have? Using
thisin arrow functions is still valid it’s just that they will use parent scope to resolve it. You saying it doesn’t havethisorargumentsdoesn’t convey any benefits (nor real drawbacks) to me. Hence the convention feels useless at best.