Re: Output escaping PSR

On 10/5/16 12:17, Larry Garfield wrote: On 10/05/2016 05:05 PM, Korvin Szanto wrote: On Tue, Oct 4, 2016 at 4:18 PM Sara Golemon > wrote: On Tuesday, October 4, 2016 at 9:40:03 AM UTC-7, Korvin Szanto wrote: Are you thinking like a text

Re: Output escaping PSR

On 10/05/2016 05:05 PM, Korvin Szanto wrote: On Tue, Oct 4, 2016 at 4:18 PM Sara Golemon > wrote: On Tuesday, October 4, 2016 at 9:40:03 AM UTC-7, Korvin Szanto wrote: Are you thinking like a text filter PSR or more of an output

Re: Remove Developer Advocacy Requirement From Secretaries Role

Someone's got to be responsible for the website and Twitter account, which do fall under the "advocacy and marketing" umbrella, more or less. As Michael requested, I strongly suggest we not try to tinker with the bylaws further until after FIG 3 is fully in place and had some "settling in

Re: [PSR-11] Question about PSR-11

What do you mean? The namespace is simple "Psr\Container". It doesn't clarify domain. On Wednesday, October 5, 2016 at 5:19:40 AM UTC+3, Woody Gilk wrote: > > Why should a class name contain information that is present in the class > namespace? If you don't like the class name, there is the

Re: [Important] [Internals] All projects must declare intention to remain members

Phalcon remains member On Sunday, 2 October 2016 18:44:02 UTC-5, Michael Cullum wrote: > > As per the FIG 3.0 bylaws, all member projects must, between the 1st > October and 31st October, declare they wish to remain a member project of > the FIG. If you don't wish to remain, then it would be

Re: Output escaping PSR

Hi, My thinking was an output escaping spec. It is a lot more nuanced than you may initially think as there is context to consider eg you need to escape differently inside a html attribute as you do for straight onto the page, similarly for a js context or css context. An interface containing

Re: Output escaping PSR

I think it's a good idea. following.. -- 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