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

\Parable\Console\Parameter can't handle --option=value #15

Closed
devvoh opened this issue Jul 20, 2017 · 4 comments
Closed

\Parable\Console\Parameter can't handle --option=value #15

devvoh opened this issue Jul 20, 2017 · 4 comments
Assignees
Milestone

Comments

@devvoh
Copy link
Owner

devvoh commented Jul 20, 2017

It will handle --option value just fine, but the equals-sign makes it not recognise the option.

Maek fix do work proper.

@devvoh devvoh added this to the 0.12.5 milestone Jul 20, 2017
@devvoh devvoh self-assigned this Jul 20, 2017
@jerry1970
Copy link
Contributor

Is --option=value a proper syntax? I've never seen it.

@devvoh
Copy link
Owner Author

devvoh commented Jul 20, 2017

It is. The ecosystem standard is Symfony Console, whether I like it or not. Composer uses it, and that's a major part of the current ecosystem (as you well know).

So check out the following: https://symfony.com/doc/current/components/console/console_arguments.html

I don't currently offer arguments at all, figuring values-optional option parameters offer all the functionality I personally need.

I've considered adding arguments, but I'm not sure. Any input from different viewpoints would be appreciated.

@jerry1970
Copy link
Contributor

If --option=value is a common way to pass arguments to the script, it would indeed be very nice to see this format accepted, so agree with your inital post to fix that.

Regarding arguments, I have several command line scripts that accept arguments, so I would be in favour of including those as well. Low priority, though.

devvoh added a commit that referenced this issue Jul 22, 2017
@devvoh
Copy link
Owner Author

devvoh commented Jul 22, 2017

Should be fixed in 0.12.5. Reopen if it requires fixes!

@devvoh devvoh closed this as completed Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants