Expected an indentation at 22 instead of at 21. Wontfix
value: @seed.saved_at ? @seed.saved_at.to_fs(:ymd) : '',
- Create a ticketCreate a ticket
- Exclude checks
Expected an indentation at 22 instead of at 21. Open
class: 'add-datepicker', label: 'When were the seeds harvested/saved?'
- Create a ticketCreate a ticket
- Exclude checks
Line is too long. [139/120] Open
.col-md-6= f.number_field :days_until_maturity_max, label_as_placeholder: true, label: 'max', prepend: 'to', append: "days", min: 1
- 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: 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.
Line is too long. [126/120] Open
= f.select(:tradable_to, Seed::TRADABLE_TO_VALUES, {label: 'Will trade', wrapper: { class: 'required'}, required: true})
- 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: 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.
Line is too long. [140/120] Open
= f.select(:organic, Seed::ORGANIC_VALUES, {label: 'Organic?', wrapper: { class: 'required'}, required: true}, default: 'unknown')
- 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: 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.
Line is too long. [128/120] Open
= f.select(:gmo, Seed::GMO_VALUES, {label: 'GMO?', wrapper: { class: 'required'}, required: true}, default: 'unknown')
- 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: 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.
The = symbol should have one space separating it from code Open
%strong=yield :title
- Read upRead up
- Create a ticketCreate a ticket
- Exclude checks
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.
Line is too long. [125/120] Open
= f.text_field :finished_at, class: 'add-datepicker', value: @seed.finished_at ? @seed.finished_at.to_fs(:ymd) : ''
- 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: 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.
Line is too long. [143/120] Open
= f.select(:heirloom, Seed::HEIRLOOM_VALUES, {label: 'Heirloom?', wrapper: { class: 'required'}, required: true}, default: 'unknown')
- 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: 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.
Line is too long. [140/120] Open
.col-md-6= f.number_field :days_until_maturity_min, label_as_placeholder: true, label: 'min', prepend: 'Days until maturity', min: 1
- 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: 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.