On Fri, Jun 13, 2025, at 9:10 AM, Andreas Heigl wrote:
> 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 ;-) :
>
> 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.
>
> But it also doesn't make sense to only have the pasckage and no overview.
>
> 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!)
>
> The order was not meant as an order of importance! IMO *both* are important!
>
> Cheers
>
> Andreas

Ah, that was unclear, and it sounded like some folks were advocating for just 
the markdown file (registry).  I'm fine with generating a markdown file off of 
docblocks or whatever, as long as there is a code package.

In that case, I volunteer as tribute!

--Larry Garfield

-- 
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/70e1d8a0-9521-447e-bb2b-3d25fd8b2140%40app.fastmail.com.
  • Re: Creating a Re... Matteo Beccati
    • Re: Creating... 'Andreas Heigl' via PHP Framework Interoperability Group
      • Re: Crea... Matteo Beccati
      • Re: Crea... Ben Ramsey
        • Re: ... Larry Garfield
          • ... Navarr Barnier
            • ... Jaap van Otterdijk
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Larry Garfield
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Larry Garfield
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Korvin Szanto
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Korvin Szanto
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
              • ... Larry Garfield
              • ... 'Andreas Heigl' via PHP Framework Interoperability Group
        • Re: ... Eric Fortmeyer
  • Re: Creating a Re... Vincent de Lau
  • Re: Creating a Re... Larry Garfield

Reply via email to