Re: Found a typo in fig-standards; made a pull request

PR has been updated - thanks for the feedback! For this PR I manually copypasted the documents into Grammarly.com's online tool to check the grammar and spelling. Unfortunately, I don't think they have an API, and I'm unfamiliar with any automated tools which could be used instead. (Perhaps

Re: [PSR-13] URI templates and URI objects

On 06/20/2016 03:28 PM, Larry Garfield wrote: On 06/16/2016 03:38 PM, Matthew Weier O'Phinney wrote: On Wed, Jun 15, 2016 at 3:31 PM, Larry Garfield wrote: A corresponding PR has been filed here: https://github.com/php-fig/fig-standards/pull/775 Including the

Re: The CLI interface PSR brainstorm

In general, my response to these comments are that you could make similar arguments for basically any PHP software component. If the FIG was to standardise every aspect of framework development, we would end up with a FIG framework that was no different from the others and actually worked

Re: The CLI interface PSR brainstorm

Am 07.07.16 um 10:35 schrieb Andrew Carter: > I don't see this as an area where interoperability is better than > innovation, but I could be persuaded. I think the FIG has to be careful > not to standardise things for the sake of it - because it could be done > - but rather because it would be

Re: The CLI interface PSR brainstorm

Sure, actually I already did in this thread. Look at doctrine migrations provider for silex: https://github.com/kurlltd/silex-doctrine-migrations-provider If the CLI is standardized as an interface the next step would be standardizing the Command interfaces, making such glue classes unneeded, and

Re: The CLI interface PSR brainstorm

I don't see this as an area where interoperability is better than innovation, but I could be persuaded. I think the FIG has to be careful not to standardise things for the sake of it - because it could be done - but rather because it would be beneficial to the ecosystem to do so. Composer