-
Notifications
You must be signed in to change notification settings - Fork 24
Globalize loopback-angular-sdk-cli #46
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
Conversation
|
@slnode test please |
That's fine, I agree it's better to have a Just make sure the "scripts" entry in package.json on line 6 keeps working after rename. When users install via ATM, we have "lb-ng": "bin/lb-ng"I don't know if "lb-ng": "bin/lb-ng.js" |
|
@0candy PTAL |
| var generator = require('loopback-sdk-angular'); | ||
| var SG = require('strong-globalize'); | ||
| SG.SetRootDir(path.resolve(__dirname, '..')); | ||
| var g = SG(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be at the beginning of the file.
|
Changes LGTM. Please squash before merge. |
note that `lb-ng` is changed to `lb-ng.js` because slt-globalize checks files based on file extension
|
@slnode test please |
1 similar comment
|
@slnode test please |
@bajtos stl-globalize uses file extensions to determine what gets globalized, I have updated the name to
lb-ng.js(fromlb-ng), is there any particular advantage or reasons we shouldn't change it? I can see it being more likely to be skipped by lint as well.@0candy PTAL
/cc @Setogit
related to strongloop/loopback#2422