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.

Style/ClosingParenthesisIndentation has the wrong namespace - should be Layout

See original GitHub issue

Hi there, I need help with an issue I’m having with VS Code rubocop integration that never used to show up. I’m getting a pop up on every single Ruby file that says Style/ClosingParenthesisIndentation has the wrong namespace - should be Layout, so I update the .rubocop.yml file to Layout, and then I get Layout/ClosingParenthesisIndentation has the wrong namespace - should be Style. As you could imagine, this is very frustrating. How can I fix this?

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:15
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

6reactions
yusefucommented, Apr 26, 2018

To fix it just replace in your .rubocop.yml file Style by Layout.

# change this
Style/ClosingParenthesisIndentation
# to this
Layout/ClosingParenthesisIndentation
1reaction
Hbbbcommented, Apr 26, 2018

@yusefu You’re correct, that does solve the issue. What I was calling attention to is the fact that the Rubocop binary still lints the file despite these warnings. I was hoping to see the same behavior implemented in this extension. I’m happy to help contribute 😀

Read more comments on GitHub >

github_iconTop Results From Across the Web

Visual Studio 2019 closing curly brace not under the opening ...
My guess is that your bracing/indentation is busted and needs to be reset. To get there: Tools ->> Options ->> Text Editor ->>...
Read more >
Code Style Guidelines - WebKit
The contents of namespaces should not be indented. Right: // Document.h namespace WebCore { class Document { Document(); ...
Read more >
The Clojure Style Guide
When we had to choose between a very established practice and a ... bad - argument aligned with function name (one space indent)...
Read more >
PSR-2: Coding Style Guide - PHP-FIG
The opening brace for the class MUST go on its own line; the closing brace for the class MUST go on the next...
Read more >
Formatting 2 - Style Guide of Common Languages - Educative.io
You must also have a space between the close parenthesis and the curly brace, ... namespace {. 2. ​. 3. // Wrong! Indented...
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