The problem is some things shouldn't be framework-agnostic, because they *are* framework. They are what make us to choose one framework in favour of another. Here is place for personal preferences. I'd be careful with proposals like "because we can".
On Monday, June 27, 2016 at 10:57:46 AM UTC+3, Dracony wrote: > > A year or maybe two ago I proposed a PSR for "tasks", that would allow > easier chaining of common things like e.g. migrating a database, minimizing > CSS, etc. Back then it didn't really get much traction I believe because > PHP world isn't really requiring as much build chains as say JS world > (where gulp and Grunt plugins are abundant). > > So instead I wanted to rephrase it now as a Command PSR, which is > basically standardizing something akin to Symfony Command, which would be > really really useful, since then you wouldn't need a special service > provider to get Doctrine migrations in Silex, etc. A common interface would > be very simple to achieve, but it requires standardizing the CLI interface > first. So let's do that! > > Ok, so to describe the CLI interface we need: > > > - Input/Output streams for input, output and error > - Methods to get options and arguments > - Method to get current working directory > > Getting this PSR done will open the way for the Command PSR too, and that > will be just as useful to the CLI world and Middleware PSRs are for HTTP > world. > > What do you think? Did I catch your attention? If so, let's get cracking =) > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/ca1b3a42-8c48-41fd-bcfc-20407bd946df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
