Problem/Motivation

In #2114069: Routing / tabs / actions lack way to attach context to UI strings we are adding context to UI strings to handle the case of ambiguous items like "Extend" and "Views". However tabs / routes / actions may also equally need title replacement values. The menu system supported these so this is a regression that we only allow static strings. This results in problems that derivative tab titles, eg. 'Translate @type' don't work, where we'd derive @type from elsewhere. See #2119497-9: Default local tasks are not to be assumed $route_name . '_tab' point 1.

Proposed resolution

Add support for replacement arguments that routes/tabs/actions would be able to provide. This will round out the arguments of t() to be supported.

Remaining tasks

- Do it.
- Write tests.
- Review.
- Commit.

User interface changes

None.

API changes

TBD

#2114069: Routing / tabs / actions lack way to attach context to UI strings

Comments

tim.plunkett’s picture

Issue summary: View changes
Issue tags: +MenuSystemRevamp
dawehner’s picture