- Aug 10, 2017
-
-
greenkeeper[bot] authored
-
Paul Kaplan authored
-
- Aug 08, 2017
-
-
greenkeeper[bot] authored
-
greenkeeper[bot] authored
-
- Aug 03, 2017
-
-
Paul Kaplan authored
-
- Jul 31, 2017
-
-
greenkeeper[bot] authored
-
- Jul 21, 2017
-
-
Paul Kaplan authored
-
Paul Kaplan authored
-
- Jul 19, 2017
-
-
chrisgarrity authored
Dynamic import didn’t do what we wanted, so just added `npm run i18n:msgs` to the start command. This is just temporary. Other changes as requested: * exports in one place * loc=> locale Also fixed use of require for localeData to use dynamic import (this one works), so the babelrc changes are needed, otherwise import as a function is not recognized.
-
Paul Kaplan authored
-
Paul Kaplan authored
-
- Jul 18, 2017
-
-
chrisgarrity authored
Using react-intl-redux package. This just sets up the default English. Language switching in another PR. Requires locale/messages.json to exist, `{}` is ok.
-
chrisgarrity authored
Generate `locale/messages.json` from available languages in `translations`. If there are no translations for a given language (from `languages.json`) it just skips it, react-intl will use the default english strings. Just using English, French and Spanish for testing right now.
-
- Jul 17, 2017
-
-
chrisgarrity authored
Generating the localization source to update the translation system (transifex) is really separate from building. When building we want to be using the current state of translations from transifex, and the english default strings are not needed. Uses the babel-cli to run the babel-plugin-react-intl separately from webpack.
-
chrisgarrity authored
Making the script easier to reuse later.
-
chrisgarrity authored
Using babel-plugin-react intl to extract messages from sources that use react-intl. It creates one file per component, that’s not ideal for translators. Transifex supports several different json formats. We picked the chrome i18n json format because it includes the ‘description’ and displays that to translators as instructions in the transifex UI.
-
- Jul 11, 2017
-
-
greenkeeper[bot] authored
-
- Jul 06, 2017
-
-
greenkeeper[bot] authored
-
- Jun 30, 2017
-
-
chrisgarrity authored
Costumes and Sound tab strings.
-
greenkeeper[bot] authored
Closes #429
-
Susie Sahim authored
-
- Jun 28, 2017
-
-
greenkeeper[bot] authored
-
- Jun 26, 2017
-
-
Paul Kaplan authored
-
- Jun 24, 2017
-
-
greenkeeper[bot] authored
-
- Jun 22, 2017
-
-
Paul Kaplan authored
-
- Jun 17, 2017
-
-
greenkeeper[bot] authored
-
- Jun 15, 2017
-
-
greenkeeper[bot] authored
-
greenkeeper[bot] authored
-
- Jun 14, 2017
-
-
greenkeeper[bot] authored
-
Ray Schamp authored
In case the remote one gets deleted for some reason. I already had a fork of gh-pages, which is why I'm using rschamp rather than LLK. This is intended to be temporary.
-
- Jun 13, 2017
-
-
Susie Sahim authored
-
Susie Sahim authored
Configure Jest to mock svgs and css so that it doesn't throw syntax errors. This is also per recommendation in the Jest docs: https://facebook.github.io/jest/docs/webpack.html
-
Susie Sahim authored
WIP getting a react test working. Throws syntax error on svgs so need to maybe configure jest to use existing webpack config instead which probably properly handles svgs. - added additional plugins to get tests working
-
- Jun 10, 2017
-
-
Susie Sahim authored
\o/ Successfully got hello world of jest working on windows (in windows cmd line). For some reason git bash doesn't work.
-
Susie Sahim authored
-
Susie Sahim authored
-
Susie Sahim authored
-
- Jun 09, 2017
-
-
Ray Schamp authored
-
Ray Schamp authored
Currently using an unmerged PR in gh-pages. (Will update to an LLK fork if we decide to go this way.) Move to Travis build stages to handle the multiple deploy methods by branch. Stop "testing" in more Node versions than 6, as this is basically just testing our build tools (using a single Node version simplifies using build stages.) Also add a `watch` command for testing static build output.
-
- Jun 02, 2017
-
-
Ray Schamp authored
-