Skip to content
This repository was archived by the owner on Jul 30, 2019. It is now read-only.

Conversation

cglarsen
Copy link
Contributor

We used to not take into account what the backend told was the best fit language.
This update will use this before trying to match the list of NStack provided languages with the preferred locale.
Please give it a rough review as im not 100% into all the NStack translations use cases.

@cglarsen cglarsen changed the base branch from master to develop April 12, 2017 13:52

/// In memory cache of the last language object.
public fileprivate(set) var currentLanguage: Language?
public var currentLanguage: Language?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be changeable outside the framework? I think this property should stay public read-only with internal setter. For the language overriding feature users can use the languageOverride property.

return languageDictionary
}
}
// Take preferred language form backend

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

form -> from :)

@dominik-hadl dominik-hadl merged commit 58d1b2d into develop Apr 20, 2017
@dominik-hadl dominik-hadl deleted the hotfix/languageMatchingRedone branch April 20, 2017 15:25
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants