We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are a number of issues logged on this repo which would be trivial to implement if sspak was written on top of the Symfony console component.
Benefits include:
It would require a major version bump (probably) and a fair amount of work, but probably worthwhile in the long run.
The text was updated successfully, but these errors were encountered:
Sure - I've thought this too - but it's just is the effort worth the return?
Sorry, something went wrong.
In the long run it probably is, although it might be hard to see right now
Yep - and there's the problem, does anyone have the time to do it now?
I've kind of started this lightly here: https://github.com/dhensby/sspak/tree/pulls/symfony-console
No branches or pull requests
There are a number of issues logged on this repo which would be trivial to implement if sspak was written on top of the Symfony console component.
Benefits include:
It would require a major version bump (probably) and a fair amount of work, but probably worthwhile in the long run.
The text was updated successfully, but these errors were encountered: