Skip to content
Snippets Groups Projects
  1. Jul 19, 2017
  2. Jul 18, 2017
    • chrisgarrity's avatar
      Integrate react-intl with redux · 1225d387
      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.
      1225d387
    • chrisgarrity's avatar
      Generate messages json from available translations · 0d4fcf11
      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.
      0d4fcf11
  3. Jul 17, 2017
    • chrisgarrity's avatar
      Generate i18n source separate from build step · 7e64c897
      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.
      7e64c897
    • chrisgarrity's avatar
      Parameterize script · ba53b1c7
      chrisgarrity authored
      Making the script easier to reuse later.
      ba53b1c7
    • chrisgarrity's avatar
      Generate en.json from translation messages · 88171110
      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.
      88171110
  4. Jul 11, 2017
  5. Jul 06, 2017
  6. Jun 30, 2017
  7. Jun 28, 2017
  8. Jun 26, 2017
  9. Jun 22, 2017
  10. Jun 17, 2017
  11. Jun 15, 2017
  12. Jun 14, 2017
  13. Jun 09, 2017
    • Ray Schamp's avatar
      ba6f6a97
    • Ray Schamp's avatar
      Deploy all branches but master to subdirectories · 99bb4fea
      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.
      99bb4fea
  14. Jun 02, 2017
  15. Jun 01, 2017
    • Ray Schamp's avatar
      Pin to `latest` for 3.0 modules · 8fe06537
      Ray Schamp authored
      Reverts #335.
      
      Pinning to `^0.1.0.prerelease.0` is not equivalent to `latest`, since has the effect of not installing the latest version on `npm install`, you have to also do `npm update`. This hurts us ergonomically on `npm install`, and doesn't help us since we already are releasing breaking changes on `prerelease`.
      8fe06537
  16. May 25, 2017
  17. May 22, 2017
  18. May 20, 2017
  19. May 19, 2017
  20. May 18, 2017
  21. May 11, 2017
  22. May 04, 2017
Loading