Incorrect highlighting inside strings about jetbrains-plugin-st4 HOT 5 CLOSED

Hi. Oddly enough, that is correct behavior. <int> It is a StringTemplate expression referring to an attribute called int using the default angle bracket delimiters.

from jetbrains-plugin-st4.

Then why doesn't StringTemplate interpret it as such? I get no "undefined attribute" warning and

typeMap ::= [
  "list\<int>": "std::vector\<int>",
  "list\<long>": "std::vector\<long>",
  "list\<float>": "std::vector\<float>",
  "list\<double>": "std::vector\<double>"
]

doesn't work as expected (<if(typeMap.(attribute))> evaluates to false when attribute == "list<double>").

If I change my template to:

typeMap ::= [
  "list<int>": "std::vector\<int>",
  "list<long>": "std::vector\<long>",
  "list<float>": "std::vector\<float>",
  "list<double>": "std::vector\<double>"
]

Then the backslashes appear in the output.

So this is either a bug in StringTemplate itself or in the plugin.

from jetbrains-plugin-st4.

It is because of lazy evaluation. bad attrs can only be detected at ST exec time. Those are usueble as templates not just strings...maybe that is the source of confusion. Hmm...let me verify strings can be templates.

from jetbrains-plugin-st4.

Ok, in that case both the highlighting and StringTemplate's behavior would make sense. It's still very confusing, though.

from jetbrains-plugin-st4.

@Moritz90 I think that this is because the key is just a plain string but the value is interpreted as a template.

from jetbrains-plugin-st4.