Sign upLogin

Growstuff/growstuff

View on GitHub
Star
app/views/home/_activities.html.haml

Summary

Maintainability
Test Coverage

Expected a newline at the end of the file.
Open

            by #{activity.owner_login_name}
Severity: Minor
Found in app/views/home/_activities.html.haml by editorconfig

Files should end with a trailing newline
Open

            by #{activity.owner_login_name}
Severity: Info
Found in app/views/home/_activities.html.haml by haml-lint

HamlLint/FinalNewline

Files should always have a final newline. This results in better diffs when adding lines to the file, since SCM systems such as git won't think that you touched the last line if you append to the end of a file.

You can customize whether or not a final newline exists with the present option.

Configuration Option Description
present Whether a final newline should be present (default true)

Line is too long. [130/120]
Open

    = link_to activity_path(slug: activity.slug), class: 'list-group-item list-group-item-action flex-column align-items-start' do
Severity: Info
Found in app/views/home/_activities.html.haml by haml-lint

HamlLint/LineLength

Option Description
max Maximum number of columns a single line can have. (default 80)

Wrap lines at 80 characters. You can configure this amount via the max option on the linter, e.g. by adding the following to your .haml-lint.yml:

linters:
  LineLength:
    max: 100

Long lines are harder to read and usually indicative of complexity. You can avoid them by splitting long attribute hashes on a comma, for example:

%tag{ attr1: 1,
      attr2: 2,
      attr3: 3 }

This significantly improves readability.

There are no issues that match your filters.

Category
Status