Draft: feat: #3276537 Support language specific entity tokens.

First draft - not sure yet this is really where this should go:

  • Not to big of a a fan of the t:* prefix but not prefixing the language codes feels odd too.
  • Not a fan of the necessary recursion stop in the tree builder. Not a fan of the need nor the current implementation - didn't have a better idea yet.
  • Not a fan that [entity:t:*] is not nicely grouped - maybe should represented by a dedicated token type?
  • Figure out if we can get rid of the new token type per translatable entity type e.g. by having a translatable entity type data-type, which can be used in needs-data. Afraid this might convolute the chain generation of tokens as it is not as concrete as a single data-type.

Closes #3276537

Edited by Peter Philipp

Merge request reports

Loading