Expected a newline at the end of the file. Open
= link_to t('photos.show.seed', seed: seed.to_s, owner: seed.owner.to_s), seed_path(seed)- Create a ticketCreate a ticket
- Exclude checks
Line is too long. [121/120] Open
= link_to t('photos.show.harvest', crop: harvest.crop.name, owner: harvest.owner.to_s), harvest_path(harvest)- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
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: 100Long 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.
Files should end with a trailing newline Open
= seed_icon- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
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. [125/120] Open
= link_to t('photos.show.planting', planting: planting.to_s, owner: planting.owner.to_s), planting_path(planting)- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
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: 100Long 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.