Re: [PSR-12] Survey for outstanding issues

2017-01-20 Thread Vinícius Dias
Hello, everyone! I miss a traits conflict resolution example in the PSR-12 documentation. Wouldn't it be helpful? Thanks in advance! -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and st

Re: [PSR-12] Survey for outstanding issues

2016-12-20 Thread Amo Chohan
Thank you Glen, I see that the subject has been discussed but I couldn't take away a definitive conclusion. In my humble opinion, I think the blank line should be enforced. It's cleaner, consistent and improves readability (of course that point may be subjective). On Saturday, 17 December 2016

Re: [PSR-12] Survey for outstanding issues

2016-12-17 Thread glen-84
Amo, see https://groups.google.com/forum/#!topic/php-fig/kIqR-7WI690 FWIW, I also prefer to have the blank line. On Tuesday, 13 December 2016 12:12:58 UTC+2, Amo Chohan wrote: > > Does anyone have any thoughts on this? > > > On Monday, 17 October 2016 18:22:09 UTC+1, Korvin Szanto wrote: >> >> Hi

Re: [PSR-12] Survey for outstanding issues

2016-12-13 Thread Amo Chohan
Does anyone have any thoughts on this? On Monday, 17 October 2016 18:22:09 UTC+1, Korvin Szanto wrote: > > Hi All, > I've been dragging my feet a bit on getting this survey completed and put > out there, but I think we're now ready to get some real feedback. We will > be accepting responses to

Re: [PSR-12] Survey for outstanding issues

2016-12-01 Thread Amo Chohan
Hi all, This might not be the correct place to post this (please point me in the right direction if, that's the case) but I have some thoughts on the topic of blank lines after the opening From what I can see, there's some inconsistency in having a blank line after the opening tag. The examples

Re: [PSR-12] Survey for outstanding issues

2016-11-29 Thread Korvin Szanto
We're still gathering responses from a few member projects unfortunately. We will announce results once those are in. Best wishes, Korvin On Fri, Nov 25, 2016 at 11:26 AM glen-84 wrote: > What were the results? > > > On Monday, 17 October 2016 19:22:09 UTC+2, Korvin Szanto wrote: > > Hi All, > I

Re: [PSR-12] Survey for outstanding issues

2016-11-25 Thread glen-84
What were the results? On Monday, 17 October 2016 19:22:09 UTC+2, Korvin Szanto wrote: > > Hi All, > I've been dragging my feet a bit on getting this survey completed and put > out there, but I think we're now ready to get some real feedback. We will > be accepting responses to this survey for a

Re: [PSR-12] Survey for outstanding issues

2016-10-19 Thread 'Alexander Makarov' via PHP Framework Interoperability Group
Noted https://github.com/cs-extended/fig-standards/issues/39 On Tuesday, October 18, 2016 at 4:48:58 PM UTC+3, Iltar van der Berg wrote: > > Hello, > > I'm missing decisions on a few php 7.1 implementations. I don't know if > they are considered but it saves another PSR just for a few incoming >

Re: [PSR-12] Survey for outstanding issues

2016-10-18 Thread Iltar van der Berg
Hello, I'm missing decisions on a few php 7.1 implementations. I don't know if they are considered but it saves another PSR just for a few incoming changes: Multiple exceptions in one catch: https://wiki.php.net/rfc/multiple-catch Class constant visibility modifiers: https://wiki.php.net/rfc/c

Re: [PSR-12] Survey for outstanding issues

2016-10-17 Thread Aken Roberts
Hi Korvin. FYI: on Page 13 entitled "Return Type Declaration", the sub-header "Class instantiation parenthesis" is duplicated from the previous page. Cheers, Aken -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsu