Download the PHP package stubbles/reflect without Composer

stubbles/reflect

Reflection helper functions and annotations.

Build status

Installation

stubbles/reflect is distributed as Composer package. To install it as a dependency of your package use the following command:

composer require "stubbles/reflect": "^10.0"

Requirements

stubbles/reflect requires at least PHP 8.2.

Additionally it uses stubbles/sequence to return sequences from some of the functions, and stubbles/values to parse values from annotations.

Reflection helper functions

All functions are in namespace stubbles\reflect.

reflect()

Available since release 3.1.0

To provide more convenience a function stubbles\reflect\reflect() is provided. It allows to reflect classes, objects and methods:

Since release 4.0.0, it also allows to reflect functions: `

reflectConstructor(): \ReflectionMethod

Shortcut for reflect($someObject, '__construct')

methodsOf($class, $filter = null): \stubbles\sequence\Sequence

Returns a sequence of all methods of given class.

propertiesOf($class, $filter = null): \stubbles\sequence\Sequence

Returns a sequence of all properties of given class.

parametersOf($classOrFunction, $methodName = null): \stubbles\sequence\Sequence

Returns a sequence of all properties of given class.

parametersOfConstructor($class): \stubbles\sequence\Sequence

Shortcut for parametersOf($classOrFunction, '__construct').

parameter($name, $classOrFunction, $methodName = null): \ReflectionParameter

Returns parameter with given name from referenced function or method.

constructorParameter($name, $class): \ReflectionParameter

Shortcut for parameter($name, $class, '__construct').

Annotations

For details about the concept behind annotations see annotations which contains a general introduction into the topic. For more details how to use this in a programming language see Java annotations.

How to define an annotation

Annotations can be defined on every element that can get a docblock comment: functions, methods, classes and properties. Additionally it is possible to define annotations for parameters in the docblock comment of the function or method where the parameter is part of.

In the above example you can see five different ways of defining an annotation. However, you can combine these ways as you like. You may have a casted annotation with no, one or more values. But lets go through all defined annotations.

• @MyAnnotation This is an annotation without any value.
• @AnnotationWithValues(bar='dummy', baz=42, required=true) This annotation has two values with the parameters bar, baz and required. One is a string, the other is an integer, and the last a boolean.
• @AnnotationWithOneValue("anotherDummy") This annotation has only a single string value.
• @CastedAnnotation[MyAnnotation] A casted annotation can be used distinguish between a marker and a hint which concrete actions the annotation consuming class should do. The first name is the marker, and the name part in square brackets denotes the action to follow.
• @ParamAnnotation{param}(key='value') This annotation is a parameter annotation defined for the parameter $param of the method aMethod(). The name in the curly braces denotes the name of the parameter this annotation is for. Please be aware that this annotation is not available when retrieving it via annotationsOf('Foo', 'aMethod'), this will result in a ReflectionException.

In contrast to other implementations it is not required to create a separate class for the annotation.

Read annotations

To get a list of all annotations of an annotatable element call the stubbles\reflect\annotationsOf() function. It returns an instance of stubbles\reflect\annotation\Annotations and supports the following invocations:

As convienience function to retrieve annotations of a class' constructor the function stubbles\reflect\annotationsOfConstructorParameter() can be used:

As convienience function to retrieve annotations of a function or method parameter the function 'stubbles\reflect\annotationsOfParameter()` can be used:

Read values from annotations

As seen above annotations can have values. If we take the @AnnotationWithValues from the class above this is how you can access them:

These are the possibilities:

• Boolean values can be retrieved using the method is followed by their name.
• Any other value types can be retrieved using the method get followed by their name, as property of the annotation class, or using the getValueByName() method. Please note that boolean values can also be retrieved using the get method syntax, but most times it just doesn't look that good: getRequired() has a different connotation than isRequired() from the point of view of the reader of your code.

In case the annotation has an unnamed value only it can be retrieved using $annotation->value or $annotation->getValue().

Using the method syntax with get has the advantage that a default value can be supplied which will be returned in case a value with this name is not set:

The default value for the is method syntax is false.

If values are optional their existence can be checked: $annotation->hasValueByName('bar') returns true if a value with the name bar is set, and false otherwise.

When parameter values are read they are parsed using stubbles\values\Parse from stubbles/values. See documentation of this package how values are parsed.

Annotation cache

As parsing annotations is quite expensive Stubbles will cache annotations once they are read. However, the cache by default works only on a per request base and is not persistent. In order to make the annotation cache persistent between different requests the application needs to provide an annotation cache persistence.

The simplest way to do so is to call stubbles\reflect\annotation\persistAnnotationsInFile('/path/to/some/cachefile.cache') which will then use the file named in the argument to persist the annotation cache inbetween requests.

If a cache file doesn't suit your needs you can also provide a different persistence. To do so, you need to call stubbles\reflect\annotation\persistAnnotations() and provide two functions, one which is able to read the data and return it, and another one which can receive data and store it. For a file cache implementation, this would look like this:

The first function must return the stored annotation data. If no such data is present it must return an empty array.

The second function must store passed annotation data.

Please note that if you use a persistent annotation cache that you need to be able to clear this cache, as changes in your code on annotations will not lead to an update of the cached data. This might lead to confusion on why a changed annotation will not be respected when the code is executed.