I don’t know, where I work that would get flagged. Actually, I think the linter flags this so it’s actually impossible to merge that. As to your points:
easier to understand for beginners, sometimes they don’t know about the implicit return
As a professional developer, I don’t write code for beginners - I work with professionals. If they don’t understand what the implicit return is, they don’t work here. And everything looks strange until you get used to it. And this is something that you will be seeing a lot.
easier to add additional code above the return statement
Yeah, that’s a slight pain, but very minor and rare.
easier to see the current object properties
I don’t understand, I can see them just fine in every example.
easier to add additional object properties
Again, I’m not seeing what is difficult about adding a property to any of the examples.
but: more code
Yeah, that’s a thing. When you’re working on a codebase of 110k lines with 40 other developers, keeping things tight can be a good thing. Obviously you can go too far. I’m all for taking up extra lines if it adds something to the code - readability is a big thing. But once you are used to arrow functions and implicit returns, they are no more difficult to read than regular functions - it’s just about familiarity. We shouldn’t use the readability argument to write extra code to appease people that haven’t become as comfortable with the language as they should.
When I first saw arrow functions they looked bat crap crazy and made no sense. Now they are second nature and I write almost no regular functions - generator functions being the exception. And it’s expected (actually the linter makes it “required”) to use the implicit return when it makes sense. I can’t speak to other work places, but that’s mine. And it makes sense to me.