haml-lint issues always show either warning or error
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
- Certain cops are being bucketed incorrectly. For example, "Line length too long" is coming up as a warning instead of a lower level severity. See https://github.com/ManageIQ/manageiq/pull/3126#issuecomment-111466039 for an example
- On that same example, it shows line length max as 80, when the it should be 120. This implies it's not honoring the .haml-lint file properly.
@skateman Can you figure these out?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the .haml-lint configuration and the behavior shown in the linked ManageIQ pull request comment. Verify how cop severities and the configured line-length limit are read, then confirm that the example reports the intended lower severity and a maximum of 120.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100