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.

[Bug] Rule #1005 ignores comment lines

See original GitHub issue

What happened?

An example code

Keyword1
     Keyword2

# Comment

Keyword3
     Keyword4

won’t pass the rule 1005 (empty-lines-between-keywords). The received output will be as follows:

Invalid number of empty lines between keywords (2/1)

It’s down to preferences, but as a RF user I see use cases for having e.g. keyword library section separators (and multiple other use cases) that could be done with single-line comments between keywords.

Operating System

Windows

Robocop version

2.0.2

Issue Analytics

State:
Created a year ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

bhirszcommented, Jul 29, 2022

@mnojek I agree, this will be intuitive for the users

1reaction

antonpaacommented, Jul 29, 2022

Yes, fully agreed that this would be an ideal definition!

Top Results From Across the Web

SA1005 does not allow indentation of comments #715 - GitHub

The comment starts with more than one space. This is only a violation if this is the first single-line comment in a row....

"Comment out the selected lines" option doesn't comply with ...

The current behavior of Comment Selected Lines is considered By Design. The StyleCop project introduced special rules for spacing within comments, but not...

Is it safe to retry -1005 error co… | Apple Developer Forums

Hi, I am getting -1005 and -1009 error codes intermittently on network requests ... Along the same lines, is it safe or not...

Bug listing with status RESOLVED with resolution FIXED as at ...

Bug :2 - "How do I attach an ebuild. ... Bug:520 - "please add comment about imlib use variable to make.conf ! ......

A function should have a single point of exit at the end of the ...

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your C code. All rules 311 · Vulnerability13 · Bug74 ·...