i18n: support variables as translation key

I’m submitting a … (check one with “x”)

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

I currently can’t find a way to use variable values as translation keys. I’m basically trying to do something like this:

        <select id="state" name="state" [(ngModel)]="task.state" class="form-control">
                <option *ngFor="let state of states" [value]="state" i18n>
                   {{state}}
                </option>
        </select>

where states is something like

states = ['BACKLOG', 'IN_PROGRESS', 'COMPLETED']

Expected behavior

It needs to be possible to use calculated values / variables as keys for translation

Reproduction of the problem

What is the motivation / use case for changing the behavior?

To be able to dynamically translate strings

• Angular version: 2.0.1

• Browser: [all ]

• Language: [all]

[ocombe]

It’s blocked until some big changes to the compiler are done, so yes still a few months to wait unfortunately

[ocombe]

Yes that’s no possible with dynamic variables right now. Once we can use i18n in TS code, you could easily fix your use case, the template would be the same (just remove i18n) and the code would be something like:

states = [this.i18n.__('BACKLOG'), this.i18n.__('IN_PROGRESS'), this.i18n.__('COMPLETED')]