Jeroen Engels
Jeroen Engels
> please try it out a little bit first. It might just be something you need to warm up to Sure, no problem with trying it out. > > when...
> See eslint/eslint#6211 regarding ignoring object shorthands. I agree it doesn't make sense to put those on separate lines. Ah cool! > I've had so many PRs with cluttered code...
When writing in ES5, I prefer the `declaration` style, when writing with ES2015, I think I preferred (has been a while now) writing `expression` style for short functions (`const double...
With arrow function excluded... then maybe yeah. We'll still have to mix decorated stuff like this anyway: ``` js var fn = _.curry(function (...) { ... }); ``` But yeah,...
I'm getting the same error when I do this in the `package.json`: ``` json "xo": { "space": 2, "plugin": ["lodash-fp"], "extends": ["plugin:lodash-fp/recommended"] } ``` or with the cli ``` console...
Hi @tunnckoCore! This actually used to be the case. If I recall correctly, there used to be two files: one with the list of contributors, and one with the configuration,...
(it is still beginner-friendly, just wanted the issue to be less polluted by too many labels ;) )
Can you give some examples on use-cases for this? Would it be for generating code mostly based on usages of some things? I'm slightly worried that it will be hard...
I think the proposal in my comment in https://github.com/jfmengels/elm-review/issues/121#issuecomment-1129284921 would be a better way to solve the itch.
Closing this issue seeing as @lue-bird also agrees that my proposal would fit better.