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
Lots of updates #50
Lots of updates #50
Conversation
…ded JSDoc foundation.
… rest of the commands working again. Still no prompting support.
…ing plugin, module, and sdk commands as well as handle platform specific options.
… args. More work on fixing the sdk command.
…ake into account parent options and flags. Fixed bugs with no-colors in config command. Added --output json-object to config command. Fixed argument applying in parser.
…c to the context object. More work on the help command.
…he context. Mostly finished the help command. Bug fixes and user experience improvements.
…dling when config file does not yet exist.
…orm specific options and flags to help screen.
…code cleanup. Renamed app.sdk config option to sdk.selected. Updated docs.
…ium dir does not exist and when checking if command is a non-sdk command. Major work to the info command and some more work on the setup command.
…) calls. Some cleanup on the info command, but it's currently broken. Added Node.js <0.8 fatal error.
…irs and ignoreFiles regexes. Cleaned up docs.
…d config file. Bug fixes with info command.
…n the setup command. Updated i18n strings.
…on calls so that we can use the global ignoreDirs.
…ingle values that are falsey.
…options not properly overriding global options.
} else { | ||
logger.log(__('No modules installed') + '\n'); | ||
logger.banner() |
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.
Missing semicolon
Test issue with TIMOB-13633: if you hit ctrl-c when it asks you to enter the name of the sdk to confirm, it goes ahead and uninstalls the SDK. CB: Fixed in 2d80a02 |
Build is broken on my machine. It crashes with: Error: ENOENT, no such file or directory '/Users/bhughes/Library/Developer/android-sdk-macosx/add-ons/addon-google_apis-google-10/manifest.ini' I double checked and the file doesn't exist. There is a manifest2.ini file though...because that makes so much sense of course. CB: Well, this is a bit of a bummer. For starters, you renamed it from "manifest.ini" to "manifest2.ini" to test TIMOB-13634 and was fixed in tidev/node-appc@6a97652. The problem is this fix is post 3.1.1.GA and has been sitting in node-appc and missed the 3.1.2 boat. In any case, rename the manifest back and re-test an android build. |
One of the unit tests fails: "should load module without cli arg --platform", with error "AssertionError: expected {} to have own property 'android'". I wonder if this is related to the above error? CB: Fixed in 6c59cd7 |
On a fresh install of the sdk on Linux, I get the following crash the first time the CLI is run (but not after that):
CB: Fixed in node-appc. You will need to pull the latest to test. tidev/node-appc@0194413 |
Running setup on Linux I get the following crash:
CB: Some how you are using the old CLI or something. That stack trace shows the old prompt library and the output is similar to the old setup command. |
…uninstall the sdk.
… the wrong else block.
When I run:
it seems to forget all command line options and prompts me for everything. CB: Could not reproduce even though I saw you do it. Maybe there's something I'm missing. |
…ws when there is no config.json yet. Fixed bug with ios being shown on setup command on non-Mac platforms. Fixed bug with the Android SDK path not being displayed correctly in the setup command.
Code reviewed and tested. Request Accepted |
"config" command updates