ServiceInnovationLab/RapuTure

View on GitHub
app/views/variables/_link.haml

Summary

Maintainability
Test Coverage

Files should end with a trailing newline
Open

= link_to variable.name, variable
Severity: Info
Found in app/views/variables/_link.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)

The = symbol should have one space separating it from code
Open

%span.badge.badge-secondary=variable.value_type.name
Severity: Info
Found in app/views/variables/_link.haml by haml-lint

HamlLint/SpaceBeforeScript

Separate Ruby script indicators (-/=) from their code with a single space.

Bad: no space between = and some_expression haml =some_expression

Good haml = some_expression

Good haml - some_value = 'Hello World'

Ensuring space after -/= enforces a consistency that all HAML tags/script indicators are separated from their inline content by a space. Since it is optional to add a space after -/= but required when writing %tag or similar, the consistency is best enforced via a linter.

There are no issues that match your filters.

Category
Status