Let's say I have a method that has a parameter whose real values ββare declared as class constants (think PGSQL_ASSOC / PGSQL_NUM / PGSQL_BOTH ). And there is another method with a similar parameter, using a different set of class constants. Is there a way to describe phpDocumentor that each set of constants belongs to a logical group of alternatives? It would be useful if they were documented by groups and had the ability to refer to specific groups in the documentation of the method. Using docblock templates does not shorten it, because the short description of the template is ignored (adding useless clutter), while the long description of the template is added to the description with constant binding, which leads to the form of the inverse statement (for example, βBAR_MODE_1β is true. works for Foo :: bar () "instead of" Operating modes for Foo :: bar (): BAR_MODE_1 does this and that. ").
Example:
class Foo {
lanzz source share