Syntax highlight for preferred syntax with parens
blackxored opened this issue · comments
Cucumber is now generated step definitions including parenthesis, I don't particularly like the idea but the thing is that omitting parentheses does generate a warning when running ruby -w on it, also on syntastic as well. As I said now the generated step definitions that you get when you have an undefined step do include the parens so I'm guessing this is now the preferred way to go. I updated my project through some argdo stuff but I don't know if it had something to do with it, but I'm pretty sure that's not the case. The issue comes that vim-cucumber isn't syntax highlighting any Given/When/Then/And/But keywords if they're immediately surrounded by parens like in Given(/Something that I use to know/) doesn't get highlighted. Would you please fix this, or point me in the way of doing it. My knowledge of vimscript is fairly limited even when it comes to syntax files.
That's actually handled by vim-ruby not vim-cucumber. The actual issue isn't that it fails to highlight Foo() but that it does erroneously highlight the Foo in Foo "bar" as a constant (when actually it's a method). You can open an issue there if you like, but since it's basically only an issue in cucumber steps, it's a pretty low priority for me.