Question - Difference using `t` helper and `intl.t` from the Service

• I have searched the issues of this repo and believe that this is not a duplicate

Environment

• Ember Version: 3.16.10
• Ember CLI Version: 3.16.2
• Ember Intl Version: 4.4.1

Question

Hello there, I have a small question.

I am wondering, is there a difference between using t macro helper and intl.t from the Service?

https://ember-intl.github.io/ember-intl/docs/guide/translating-text#t

import { t } from 'ember-intl';

export default class ... {
  title = t('my.key');
});

https://ember-intl.github.io/ember-intl/docs/guide/service-api#t-translationkey-string-optionaloptions-object-string-safestring

export default class ... {
  @service intl;

  constructor() {
    title = this.intl.t('my.key');
  }
});

For some cases I need @computed('intl.locale') so obviously the Service will be injected and I will use this.intl.t().

Thanks for your explanation.

[MrChocolatine]

That wouldn’t work, because you’re returning the computed property macro, not the value it would resolve to.

Ah yes, right. It seems I easily forget it is a computed property macro so indeed it won’t return the value.

Again many thanks, great explanations. It also helped other JS dev of my team.

[jasonmit]

Ensure that using this.intl.t(‘…’) in an auto-tracking context correctly entangles the locale as a dependency, so that changing the locale invalidates the getter

I believe there was an attempt to resolve this: https://github.com/ember-intl/ember-intl/pull/1340

Landed in v5.2.0, is that not working?