liviriniu

> fixing it will create a regression for anyone currently relying on it to squeeze two properties into the space of one Maybe it would help to come up with...

@nblumhardt & @mariopasquali : I looked through `MessageTemplateTextFormatter` and connected classes. I'd love to contribute to your work, Mario, if you'll take this for a PR?/separate project or to try...

I tried `@import` variants including stuff like: @import _ = MyApp.Code.EnumExtensions @import static MyApp.Code.EnumExtensions None succeeded unfortunately.

Yeees, sure. But... sigh 😿

Because then I must do the conversion in the markup for which, by the way, the intellisense does not suggest the `ToDateTime` method.  ... I was lazy in giving...

Which, although it makes the markup squiggly warning go away, it crashes with: 

BP:DatePicker simply crashes if I use DateOnly  > but can't you simply change the constructor argument to DateTime? Sure, this is how I currently go about because I have...

also, a case that frequently appears, checking for enum members:  _nice to have:_ property_of_enum_type is enum_member1 or enum_member2 or enum_member3

This would be ideal to apply to all states of the grid, including to the add/edit textbox if that is what your are referring to. In our case, `

PS: also, a `