Skip to content

Fix import command parameters#910

Merged
parkr merged 1 commit intojekyll:masterfrom
x3ro:fix-import-command-parameters
Apr 1, 2013
Merged

Fix import command parameters#910
parkr merged 1 commit intojekyll:masterfrom
x3ro:fix-import-command-parameters

Conversation

@x3ro
Copy link
Contributor

@x3ro x3ro commented Mar 31, 2013

Apparently, the Commander gem treats options as boolean values
when one does not indicate that a certain options is followed
by a string. This led to the jekyll-import gem only receiving
booleans instead of dbname/user/pwd...

Note: Haven't added a test for this, because I wasn't quite sure how I should go about writing a test for it. If someone would provide me with a pointer, I'd be happy to add a test as well.

Apparently, the Commander gem treats options as boolean values
when one does not indicate that a certain options is followed
by a string. This led to the jekyll-import gem only receiving
booleans instead of dbname/user/pwd...
parkr added a commit that referenced this pull request Apr 1, 2013
@parkr parkr merged commit 791fa3e into jekyll:master Apr 1, 2013
parkr added a commit that referenced this pull request Apr 1, 2013
@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants