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

Application should have "forced" command, rather than "default" #31

Closed
g105b opened this issue Mar 27, 2019 · 0 comments
Closed

Application should have "forced" command, rather than "default" #31

g105b opened this issue Mar 27, 2019 · 0 comments

Comments

@g105b
Copy link
Member

g105b commented Mar 27, 2019

The setDefaultCommand function is used to allow calling a command that's registered on the Application without calling the command, which is useful for applications that only have one command.

However, the function was designed with one particular use-case in mind: a command that takes only Parameters and not NamedParameters. With NamedParameters, this functionality is impossible to use.

If the setDefaultCommand function was renamed to forceCommand, this would tell the Application that the provided command should always be run.

Would be extra useful to have #15 implemented for this too.

g105b added a commit to PhpGt/Sync that referenced this issue Mar 27, 2019
@g105b g105b closed this as completed in 2f4c8b2 Mar 27, 2019
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

No branches or pull requests

1 participant