Drop `defaultLocale` in favor of iterating `locales` array? about ember-intl HOT 6 CLOSED

@ericf I kind of like having them separate, otherwise the consumer will need to be cognizant of keeping the default locale at the tail of the locales array.

This is currently how its used in ember-intl.

// pseudo-code but it's pretty similar
getMessage: function (path) {
  var locales = Ember.makeArray(this.locales); // in case the user just set a string
  locales.push(this.defaultLocale); // in the actual implementation I don't push if locales contains the defaultLocale
  for(var i=0;i<locales.length;i++) {
    var locale = this.getLocaleObject(locales[i]);
    var msg = locale.get(key);
    if (typeof msg !== 'undefined') { return msg; }
  }
}

from ember-intl.

This the way locales is suppose to work as a fallback anyways, so I think it fits. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl#Locale_negotiation

from ember-intl.

Ah, that makes sense. I'll remove it. Do you want me to update the other libs while I'm at it?

from ember-intl.

Ah, that makes sense. I'll remove it. Do you want me to update the other libs while I'm at it?

Let's discuss it first. That's why I cc'd @caridy

from ember-intl.

The result of the chat offline was to remove references to defaultLocale and then remove it from the code base when we remove it from all the other integration libs.

from ember-intl.

#67 supersedes this

from ember-intl.