Applying the @method and @property items on a class basis can deal with magic methods.
By making it a per-method property it raises a whole bunch of other questions, like - Will there be a single method that clearly owns the given magic method? - Will the arguments of the magic method be the same as the underlying method, or will there be extra/removed arguments? - Will the return type of the magic method be the same as the underlying method? In general it seems like a piece of functionality with only limited benefit over class-based @method and @property items, for a very specific use-case. On Monday, 3 April 2017 08:54:19 UTC+12, David Rodrigues wrote: > > It's how the major part of frameworks are working now, by using features > like magic methods from PHP to create some shortcuts on development. > -- 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/b994dd8e-89e1-4ec6-b170-e168e3ba32c4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
