Add token syntax validation where possible

This is probably not that hard to realize, as we'd basically just need to strip out the brackets from beginning and end, if they are available.

It's a great idea to improve UX at this point. I'd like to throw an alternative approach in: instead of being more tolerant with an officially not supported syntax, we could apply validation to token name fields, which would give the user straight feedback about the error and let them correct their model and learn from it for the future.

This would also prevent an awkward situation where someone would use [field_name:0:value] as the field name, where the silent correction would try working with field_name:0:value to still not satisfy the user as it causes different errors.

Sure, throwing a validation error instead, that's even better.

Implemented by using the proposed form field property #eca_token_reference as proposed in ✨ Tag form fields that support tokens Active .

That is really cool. I think I can provide a test here. At least I give it a try.

I have added a new test class for ECA entity.

Of course there is much more to test, but let us do this in other issues. The functionality implemented here in the issue is tested now.

The code here looks good to me.

Nice test, thanks @danielspeicher

Merged the MR and now wonder if this should be back ported? It doesn't really change the ECA functionality, it "just" improves the UX while building models.

Back ported to 1.1.x

Automatically closed - issue fixed for 2 weeks with no activity.