When the sublime linter checks javascript inside <script> blocks (in html or vue files), it uses the global indent rules that assume the inner block should start at indent 0. This means that every line of a correctly formatted script block in the style
<script>
function foo(bar) {
doSomething(bar);
}
</script>
will be incorrectly labeled as indent errors.
This should have been addressed by the eslint baseIndent option, but that was rejected (due to a policy change, rather than an issue with the change).
When the sublime linter checks javascript inside
<script>blocks (in html or vue files), it uses the global indent rules that assume the inner block should start at indent 0. This means that every line of a correctly formatted script block in the stylewill be incorrectly labeled as indent errors.
This should have been addressed by the eslint
baseIndentoption, but that was rejected (due to a policy change, rather than an issue with the change).