Skip to content
This repository has been archived by the owner on Oct 6, 2021. It is now read-only.

Provide means for I18n locale components #135

Open
matthijsgroen opened this issue Jan 16, 2017 · 1 comment
Open

Provide means for I18n locale components #135

matthijsgroen opened this issue Jan 16, 2017 · 1 comment

Comments

@matthijsgroen
Copy link
Member

Make a default way of working for having multiple translation files for a single locale, e.g.:

homescreen.en.yml, settings.en.yml

maybe even add smart loading through webpack that only a single locale file is included (omitting other locales when not used)

@matthijsgroen matthijsgroen added this to the 2.0.0 milestone Jan 16, 2017
@pascalw
Copy link
Member

pascalw commented Jan 18, 2017

@matthijsgroen I've been thinking about this.

I think there are two points to this:

  • Having an out of the box solution to split up locales into multiple files.
  • Loading only a single locale at a time.

First point shouldn't be too hard, but the second point is probably more difficult. In order to load only a single locale at a time we'd need to make sure that each language generates a separate JS bundle and load that asynchronously. That introduces all sorts of issues because loading that bundle could fail or take some time after the initial assets are loaded. Do you have any thoughts on this?

@pascalw pascalw removed this from the 2.0.0 milestone Feb 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants