Re: Creating a Registry for community provided Attributes

['Andreas Heigl' via PHP Framework Interoperability Group]

Hey Larry.

Am 13.06.25 um 15:56 schrieb Larry Garfield:

On Fri, Jun 13, 2025, at 6:33 AM, 'Andreas Heigl' via PHP Framework 
Interoperability Group wrote:

So all in all:

[snip]

 The expected outcome is a meta-document listing the attributes,
possible parameters to them and a usage for each of them. In addition a
package will be distributed that contains implementations for these
attributes to support usage in code or auto-complete.

Any additions to this? Any Objections?

Cheers

Andreas

I want to reiterate my earlier point:

A PER whose artifact is a markdown file:

* Pure - Indicates a function with no side effects.
* Internal - Indicates a function that should not be used outside this library

is, IMO, unuseful and potentially even counter productive, and I would not 
support or participate in it.

A PER whose artifact is a repository with the following in it:

namespace Fig\Attributes;

// Indicates a function with no side effects.
#[Attribute]
class Pure {}

// Indicates a function that should not be used outside this library
#[Attribute]
class Internal {}

I believe would be useful, and I would support it and be interested in joining 
it.

(Naturally some attributes will also have parameters, some not, that's a case 
by case to figure out later.)

To reiterate my previous point ;-) :





But it also doesn't make sense to only have the pasckage and no overview.



The order was not meant as an order of importance! IMO *both* are important!

Cheers

Andreas


--
                                                              ,,,
                                                             (o o)
+---------------------------------------------------------ooO-(_)-Ooo-+
| Andreas Heigl                                                       |
| mailto:andr...@heigl.org                  N 50°22'59.5" E 08°23'58" |
| https://andreas.heigl.org                                           |
+---------------------------------------------------------------------+
| https://hei.gl/appointmentwithandreas                               |
+---------------------------------------------------------------------+
| GPG-Key: https://hei.gl/keyandreasheiglorg                          |
+---------------------------------------------------------------------+

--
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 view this discussion visit 
https://groups.google.com/d/msgid/php-fig/cd8115ca-230b-4bff-b8be-45b63984ee85%40heigl.org.

The expected outcome is a meta-document *AND* a package with implementations of the actual attributes. IMO it makes no sense whatsoever to only have the meta-document and no implementation. Whether the meta-document is autogenerated from the package or manually crafted is then up to the working group (I strongly suggest to have that autogenerated!)

OpenPGP_signature.asc
Description: OpenPGP digital signature