question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

implicit-arrow-linebreak doesn't enforce closing paren location

See original GitHub issue

Tell us about your environment

  • ESLint Version: v6.5.1
  • Node Version: v8.12.0
  • npm Version: v6.9.0 (but I’m using yarn v1.15.2 for this project) What parser (default, Babel-ESLint, etc.) are you using? babel-eslint@10.0.3 Please show your full configuration:
Configuration Using eslint-config-airbnb@18.0.1
extends: airbnb
parser: babel-eslint
env:
  browser: true
rules:
  comma-dangle: [warn, always-multiline, {functions: never}]
  import/prefer-default-export: 0
  jsx-quotes: [warn, prefer-single]
  max-len: [warn, { code: 80 }]
  radix: [warn, as-needed]
  react/destructuring-assignment: [warn, always, { ignoreClassFields: true }]
  react/jsx-filename-extension: 0

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

const doSomeFoo = (foo) => (
  foo);
node_modules/.bin/eslint app/javascript/specifications/actions/form/index.js

What did you expect to happen? A warning telling me that my closing paren should be on a new line, like in the docs:

const doSomeFoo = (foo) => (
  foo
);

What actually happened? Please include the actual, raw output from ESLint. No output

Are you willing to submit a pull request to fix this bug? I have never worked on this project, so unless someone were to point me in the right direction, likely not.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
g-planecommented, Nov 20, 2019
0reactions
willlmacommented, Nov 23, 2019

Many thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

implicit-arrow-linebreak - ESLint - Pluggable JavaScript Linter
Rule Details​​ This rule aims to enforce a consistent location for an arrow function containing an implicit return.
Read more >
Reduce smelling code and detect JavaScript issues with ESLint
While real JavaScript syntax errors, such as a forgotten closing curly bracket, prevent a record from being saved, there is no (with known)...
Read more >
enforce line breaks after opening and before closing array brackets ...
It reports an error if one bracket in the pair has a linebreak inside it and the other bracket does not. Or an...
Read more >
Optional Braces - Scala 3 - EPFL
In a brace-delimited region, no statement is allowed to start to the left of the first statement after the opening brace that starts...
Read more >
eslint-plugin-coffee - npm
coffee/implicit-arrow-linebreak, enforce the location of function bodies ⚠️ Unlike the ESLint rule, the CoffeeScript version is not fixable.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found