Skip to content
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

Support arbitrary CLI options #331

Merged
merged 2 commits into from
Mar 9, 2017
Merged

Conversation

kevinrenskers
Copy link
Member

Pass all CLI options (even ones we don't know about) to themes. They can use these for theme specific things like logo paths.

Needed for wdullaer/raml2slate#3 for example.

Reason from switching away from Commander: tj/commander.js#609

…es we don't know about) to themes. They can use these for theme specific things like logo paths.
@wdullaer
Copy link

wdullaer commented Mar 9, 2017

This would work for me.
The only thing that's missing is a way to make the theme options discoverable.
That said, I don't have an immediate solution for that, at least not one which requires rewriting big chunks of the cli.

@kevinrenskers
Copy link
Member Author

kevinrenskers commented Mar 9, 2017 via email

…cally format all code.

Called via ESLint so we benifit from the great exising editor integrations, files get formatted on save. Biggest reason to use this vs the old AirBnb style? Less config, no longer need to worry about code style, just let the tool handle all formatting.

For developers nothing really changes: still run `npm run lint` to lint (and now auto format) all JS files.
@kevinrenskers kevinrenskers merged commit 317bd35 into develop Mar 9, 2017
@kevinrenskers kevinrenskers deleted the arbitrary-cli-options branch March 9, 2017 22:15
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants