RuboCop: Lint/Syntax: unexpected token tSYMBOL and kEND about haml-lint HOT 5 CLOSED

So thanks for the report. Unfortunately, I would say the problem is in your code.

From my testing, this (your code) is not valid ruby code:

render 'devise/shared/error_messages', resource:
f.hidden_field :reset_password_token

Try it in a file and try to run rubocop or even just plain ruby on it. Same error.

Or try it in an irb console (with a def, so that it's all treated at once):

def foo
  render 'devise/shared/error_messages', resource:
  f.hidden_field :reset_password_token
end

It will get refused. The code might work in HAML, and in the previous version of haml-lint. But that's just an unintended side-effect of how the code is processed (HAML adds lots of parentheses and HAML-lint used to process line by line).

It feels weird to use the shortcut of not specifying a variable without having parentheses around the call. It really feels ambiguous if the result of the next line should be used or the default variable. And this error is proof that it's ambiguous.

Your solution is to put parentheses: render('devise/shared/error_messages', resource:)

Regards,

from haml-lint.

Are you sure resource: has no arguments after it? What is the expected behavior when the value is omitted? Treat as nil?

from haml-lint.

It's a shortcut to using the variable/method with the same name. Like in JS.

I forgot this issue. I'm looking into it now.

from haml-lint.

Going to close as a question that has been answered. Thanks!

from haml-lint.

@MaxLap Thank you for such a detailed answer and the solution to my problem.
You're right, it's really feeling a bit weird to use such shorthand syntax without parentheses. Somehow I didn't ponder over it before...

from haml-lint.