Re: [Vote] Require Aura project to replace its representative

-1 from SMW and Wikibase -- 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,

Re: [Vote] Require Aura project to replace its representative

-1 from PEAR On Jul 28, 2016 18:56, "Samantha Quiñones" wrote: > All, > > The discussion period having concluded, I am now opening a vote on the > matter of the proposal to require the Aura project to name a new voting > representative. > > The discussion thread is

Re: [PSR-13] "With-er" methods

Although it's not proper english, "Wither" has the advantage to be 1. simple (with -> wither) and in line with "getter" and "setter". There may be a better word to describe those non-static factories, but "wither" is good enough IMO. Théo FIDRY Le mercredi 27 juillet 2016 15:00:29 UTC+1,

Re: [Vote] Require Aura project to replace its representative

-1 from Phalcon On Thursday, 28 July 2016 18:56:52 UTC-5, Samantha Quiñones wrote: > > All, > > The discussion period having concluded, I am now opening a vote on the > matter of the proposal to require the Aura project to name a new voting > representative. > > The discussion thread is

Re: [Vote] Require Aura project to replace its representative

-1 PPI On 29 Jul 2016 2:54 p.m., "Michael Cullum" wrote: > Judd, > > Voting is for project representatives of member projects only as per the > voting protocol[1] and only votes, not discussion or opinion polling, > should take place in this thread. > > Thanks, > Michael

Re: [Vote] Require Aura project to replace its representative

Hi, -1 from Revive Adserver On 29/07/2016 01:56, Samantha Quiñones wrote: All, The discussion period having concluded, I am now opening a vote on the matter of the proposal to require the Aura project to name a new voting representative. The discussion thread is available here:

Re: [PSR-15] FrameInterface

I think it can be both. - A FrameInterface to be used when developing middleware. - A CallableFrame class that's wrapping the callable if you really want to call it in a simple way. Maybe sometimes it's worth to have a very simple final class also in the PSR along with interfaces. For

Re: [PSR-15] FrameInterface

+1 On Friday, July 29, 2016 at 10:15:30 AM UTC-4, Matthieu Napoli wrote: > > Thanks Woody and Andrew for your answers, > > Type safety is a valid point. I'm all for type safety, however in this > case I'm not convinced it's worth it since it's just a callable that takes > a request and returns

Re: [PSR-15] FrameInterface

On 12/07/2016 15:33, Woody Gilk wrote: The term "frame" comes from Anthony Farrera: http://blog.ircmaxell.com/2016/05/all-about-middleware.html It refers to moving from one middleware frame to another. Do you have any

Re: [Vote] Require Aura project to replace its representative

-1 On Thursday, July 28, 2016 at 4:56:52 PM UTC-7, Samantha Quiñones wrote: > > All, > > The discussion period having concluded, I am now opening a vote on the > matter of the proposal to require the Aura project to name a new voting > representative. > > The discussion thread is available

Re: [Vote] Require Aura project to replace its representative

-1 from Yii. On Friday, July 29, 2016 at 2:56:52 AM UTC+3, Samantha Quiñones wrote: > > All, > > The discussion period having concluded, I am now opening a vote on the > matter of the proposal to require the Aura project to name a new voting > representative. > > The discussion thread is

Re: [PSR-15] FrameInterface

On Friday, July 29, 2016 at 5:41:07 AM UTC-4, Andrew Carter wrote: > > Type safety, IDE type hinting. > > A callable can be anything, an interface guarantees parameter types and, > in PHP 7, return types. > This dynamic property is an asset, not a liability, which is why there is so much

Re: [PSR-15] FrameInterface

Type safety, IDE type hinting. A callable can be anything, an interface guarantees parameter types and, in PHP 7, return types. Interfaces also indicate explicit implementation of the standard - rather than implicit implementation on the basis that the passed parameter could be executed. All

Re: [PSR-15] FrameInterface

Thanks. However I'm still looking for a good reason why we have this interface: why not simply `callable $next` ? - FrameInterface doesn't represent any actual usage or existing middlewares today - FrameInterface is more complex than `callable` Matthieu Le mardi 12 juillet 2016 16:39:53

Re: [PSR-17] Any help needed? When do we move forward?

Hi Woody, On 28/07/2016 17:22, Woody Gilk wrote: On Thu, Jul 28, 2016 at 10:19 AM, Paul Jones > wrote: To be clear, this is at the editor's discretion; nothing else impedes "progress." That's an interesting way to put it Paul, since you