haml files + RuboCop

[jufemaiz]

Currently seeing RuboCop errors when in HAML files.

Scopes at cursor:
- text.haml
- meta.tag.haml
- entity.name.tag.haml

RuboCop error:

%ul: unknown type of percent-literal

[Arcanemagus]

Well now I'm just confused... none of those scopes are in the list of scopes this package should trigger on...

Can you click around and run that command and see if any of the source.ruby.* scopes become active? Maybe at the very start of the file?

[Arcanemagus]

For reference, this was originally filed and discussed over in AtomLinter/linter-haml#99.

[jufemaiz]

@Arcanemagus me too ><

It's only periodic, so I'm really confused to the trigger. That I haven't determined yet. Once it happens, I need to close the project and reopen.

[quolpr]

+1, having this problem too. After file closing all become fine. I am not sure, but it appeared after last update.

[Arcanemagus]

The only way I can think of for this to happen is if part of the file is marked as one of the allowed scopes.

Do you have a file you consistently see this on that you can share? What do you get when you run Editor: Log Cursor Scopes immediately after you start seeing RuboCop messages in your Haml file?

[12eh]

I can reliably reproduce this by doing string interpolation in an attribute hash. Create a new haml file:

%a{ href: "asdfasdf" }

All good so far. Now,

%a{ href: "asdfasdf#{}" }

...and the rubocop linter kicks in. Save the file, close and reopen, rubocop errors are gone and I can continue editing. Until I do another string interpolation, anyway.

Edit: doesn't need to be in an attribute hash. = "asdf#{}" does the same thing.

[Arcanemagus]

Ah ha!

In this block:

%a{ href: "asdfasdf#{}" }

If you place the cursor in between the {} in the string interpolation part, one of the scopes is source.ruby!

Can somebody who knows HAML better file an issue on language-haml to get that marked as source.embedded.ruby (or just remove source.ruby as it already has meta.embedded.line.ruby)?

[maschwenk]

Looks like this was resolved upstream

[joelmichael]

Seems to still be happening to me.

[vzamanillo]

Seems to still be happening to me.

#48