Skip to content

Conversation

bcoe
Copy link
Member

@bcoe bcoe commented Feb 18, 2017

@nexdrew's work on introducing default command support.

Why this is cool:

  1. it allows you to use the same flow control logic for top-level execution of yargs, as is applied to sub-commands.
  2. tons of people have asked for it.

todo:

  • add tests for simple behavior.
  • add tests for behavior in conjunction with strict mode.
  • add tests for behavior when loading commands from directories.
  • document functionality.

@bcoe bcoe force-pushed the default-command-7.x branch from e151f42 to 6294c1e Compare February 18, 2017 20:12
@bcoe bcoe requested a review from JaKXz February 18, 2017 20:52
@bcoe
Copy link
Member Author

bcoe commented Feb 18, 2017

@sondr3, @m-mujica, @ahmadnassri, @vjpr, would love feedback on this feature -- definitely the feature I'm most excited about for yargs@7.

@bcoe bcoe force-pushed the default-command-7.x branch from 217cefa to 586eaba Compare February 26, 2017 07:42
Copy link

@pahdo pahdo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@bcoe bcoe changed the title [WIP] introduce support for default commands introduce support for default commands Feb 26, 2017
@bcoe bcoe merged commit b4fb629 into 7.x Feb 26, 2017
@bcoe bcoe deleted the default-command-7.x branch February 26, 2017 08:34
@ahmadnassri
Copy link

this is great!! thank you 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants