-
-
Notifications
You must be signed in to change notification settings - Fork 632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update i18n doc for .travis.yml #710
Conversation
See comment. Reviewed 1 of 1 files at r1. docs/basics/i18n.md, line 92 at r1 (raw file):
The bottom line is that this small comment, right after the clearly numbered sections, is a bit confusing. We should "just make this work". Comments from Reviewable |
Agree with your comment. The best way is to make sure i18n files are generated before building the webpack files. Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. Comments from Reviewable |
@JasonYCHuang Here is where we configure the test helper to check webpack files are ready: The best way to ensure that the localization files are built before we build the webpack files is to have the npm scripts that build the webpack files first call some rake task. If you depend on the environment, that will probably run the code you put at server startup. However, I'm not sure that we always want the code at server startup. You'd know better. Here's a rake task that just depends on server startup info: desc "Pick a random user as the winner"
task :winner => :environment do
puts "Yes -- we did something. Describe it!"
end http://stackoverflow.com/q/7044714/1009332 Then change the task to build to first have the call to create the i18n files. "build:production": "npm run build:production:client && npm run build:production:server", |
@JasonYCHuang Should we close this PR? Per #717 |
@justin808 Yes, please close this PR. |
This change is