> 1) Would it be possible to build such an interface skeleton that is sufficiently generic that it doesn't end up dictating an implementation?
Of course, we already have stream interfaces defined for PSR-7. They are much more complex than what's needed for CLI though, since CLI streams are either readable OR writeable. So the Stream API can be "borrowed" from PSR-7 and simplified. Getting the current working directory is just a a method returning a string, so there is nothing to be dictating implementation there too. All in all the "interface dictating implementation" problem doesn't come up at all really > 2) Are current CLI tool projects on board with creating a standard? > 3) What's the target audience, and how would it make life easier for the general PHP-developing public? This is rather easy. Having commands coded to a common interface would make packages like https://github.com/dbtlr/silex-doctrine-migrations obsolete. Assets management, ORM generation, running tests, etc. All these tools can ship with a command adhering to the new interface and integrate into frameworks without the need for bridges like these It'd be nice if we had Symfony representative pop up in this thread =) . Since the Symfony Console API is the de-facto standard atm On Monday, June 27, 2016 at 9:57:46 AM UTC+2, 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/7bc00196-ba51-4c44-b5e8-29f5cd018a73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
