On Tuesday, September 18, 2018 at 3:21:19 AM UTC-5, Rasmus Schultz wrote: > > I believe it's also closer to the current interpretation in PHP Storm. > > So I'd like to propose changing the definitions of these tags: > > The @api tag would be for documentation purposes only - e.g. could be used > to highlight the primary portion of the public API in a special section of > generated documentation. > > The @internal tag would work much the same as it does now, but shouldn't > be described as having any relationship with the @api tag. > > Thoughts? > >
Hey Rasmus, If we do go with keeping both tags in the PSR-19 catalog, I think we should at least change the descriptions as you've suggested here. Do you want to make a PR for that? We can always consider a drop of the @api tag as a separate discussion. CRB -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/5ee5e5b0-7c38-42cf-a4ee-8e517572031b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
