ember-cli-template-lint
Advanced tools
Changelog
v0.3.5
Update the bare-strings
rule to allow the following configuration:
true
for enabled / false
for disabledwhitelist
-- An array of whitelisted stringsglobalAttributes
-- An array of attributes to check on every element.elementAttributes
-- An object whose keys are tag names and value is an array of attributes to check for that tag name.Change default .template-lintrc.js
file value for bare-strings
to be true
, which defaults the configuration to:
{
whitelist: ['(', ')', ',', '.', '&', '+', '-', '=', '*', '/', '#', '%', '!', '?', ':', '[', ']', '{', '}'],
globalAttributes: [ 'title' ],
elementAttributes: { input: [ 'placeholder' ], img: [ 'alt' ]}
};
bare-strings
where an allowed whitelisted string would only be allowed once in a given string. i.e &&
would have failed, even though &
was a whitelisted string.Changelog
v0.3.4
bare-strings
/ html-comments
rules include line and column info.nested-interactive
rule. Usage of nested interactive content can lead to UX problems, accessibility problems, bugs and in some
cases to DOM errors. You should not put interactive content elements nested inside other interactive content elements.Changelog
v0.3.2
block-indentation
rule when a given block starts on the same line as a previous item. i.e.:{{! good }}
{{#each foo as |bar|}}
<span>{{bar.name}}:</span><span>{{bar.title}}</span>
{{/each}}
Changelog
v0.3.1
html-comments
rule which forbids the usage of HTML comments (other than <!-- template-lint bare-strings=false -->
style control comments).Changelog
v0.3.0
.template-lintrc.js
is not found).Changelog
v0.2.12
.template-lintrc.js
..template-lintrc.js
.