--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/60613603-1080-4078-b103-1dc2b232fedc%40googlegroups.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/60613603-1080-4078-b103-1dc2b232fedc%40googlegroups.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/28add8eb-e837-460a-a5aa-604a05a25d9f%40googlegroups.com?hl=en.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/60613603-1080-4078-b103-1dc2b232fedc%40googlegroups.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/25975d5f-8d54-4de4-b2fd-aabbad31e58d%40googlegroups.com.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/ed12a1df-74f0-4265-9858-77c0f897f2ee%40googlegroups.com.
1- Tag names are broken according to ABNF. Examples:
@foo\
@test-\0
identifier = (ALPHA / "_") *(ALPHA / DIGIT / "_")tag-name = identifier *("\" identifier)2- Tag names should support the same identifier format as PHP itself. That means:
3- Certain libraries also support ":" for aliasing. Namespace alias would mean fallback of N namespaces to a single alias resolution
4- There is no @override tag in the spec
5- There's no plan to coexist with possible annotation drivers, such as Addendum and Doctrine. It is mentioned, but there's no real plan to avoid each other to be consider as the alternate.
@param Map<Application\Entity\User>
6- No way to specify a Collection (read as ArrayAccess implementor) and also specify the element type it holds. Alternate example that would fix it:
@package ["Application", "Application\Entity"]Which could also take advantage of 5.4 format:@package {"Application", "Application\Entity"}
7- List are still fragile to be declared. Since we deprecate @subpackage, I may want to display the list of packages a given class is related to:
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAFp73XvKBdUdXZ8muudZuaS3QaiR_P5pzRZMGS80S2-AAOGWMQ%40mail.gmail.com.
Indeed. The entrance vote is about the meta-document and the concept of the PSR.
If it has been initially drafted, as it has in all three current entrance votes, it shouldn’t affect your vote as that is not what you are voting for.
Thanks,
Michael C
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/520DDB59.9050000%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/520E2DC3.9010006%40naderman.de.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAFp73XvNOOB9h5-hgUCK70Gke_U%3DH_A_46m77iQrke2B3D7MVA%40mail.gmail.com.
The phpDocumentor team have for a while been working on a standard for PHPDoc / DocBlock tags and definitions.
This vote is not to make it an "Accepted" PSR, and you don't need to agree with all of the wording. This vote is only to move the PHPDoc standard from Pre-Draft to Draft.If you like the idea in general, but have feedback on wording, formatting, code examples, whatever, then vote yes and send a pull request to the phpDocumentor fork now or later.
Editor: Mike van RielSponsors: Phil Sturgeon (Co-ordinator) & Donald Gilbert
This vote will come to a close August 27th at 17:00 EST.As Coordinator I am still allowed to vote on behalf of my project, so:
+1 from PyroCMS
+1 from eZ Publish
P.S. for editor/sponsors: Please find a standard way to declare array types (key and value), I only know of phplint's float[int][int], but IDE's seem to only support Type[].
On Tuesday, August 13, 2013 3:39:37 PM UTC+2, Phil Sturgeon wrote:The phpDocumentor team have for a while been working on a standard for PHPDoc / DocBlock tags and definitions.
This vote is not to make it an "Accepted" PSR, and you don't need to agree with all of the wording. This vote is only to move the PHPDoc standard from Pre-Draft to Draft.
If you like the idea in general, but have feedback on wording, formatting, code examples, whatever, then vote yes and send a pull request to the phpDocumentor fork now or later.
Editor: Mike van RielSponsors: Phil Sturgeon (Co-ordinator) & Donald Gilbert
This vote will come to a close August 27th at 17:00 EST.
As Coordinator I am still allowed to vote on behalf of my project, so:
+1 from PyroCMS
P.S: I am currently a coordinator for two proposals at the same time, which is going to be a chunk of work. I'm not trying to get involved with every PSR ever, I am just very interested in these two. I wont take on any more until these are accepted.
--
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+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/2d7ecab6-b809-480b-8f91-993f24fc5193%40googlegroups.com.
+1 from eZ Publish