1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394
|
<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter xml:id="language.attributes" xmlns="http://docbook.org/ns/docbook">
<title>Attributes</title>
<sect1 xml:id="language.attributes.overview">
<title>Attributes overview</title>
<?phpdoc print-version-for="attributes"?>
<para>
Attributes offer the ability to add structured, machine-readable metadata information
on declarations in code: Classes, methods, functions, parameters,
properties and class constants can be the target of an attribute. The metadata
defined by attributes can then be inspected at runtime using the
<link linkend="book.reflection">Reflection
APIs</link>. Attributes could therefore be thought of as a configuration
language embedded directly into code.
</para>
<para>
With attributes the generic implementation of a
feature and its concrete use in an application can be decoupled. In a way it is
comparable to interfaces and their implementations. But where
interfaces and implementations are about code, attributes are about
annotating extra information and configuration. Interfaces can
be implemented by classes, yet attributes can also be declared
on methods, functions, parameters, properties and class constants.
As such they are more flexible than interfaces.
</para>
<para>
A simple example of attribute usage is to convert an interface
that has optional methods to use attributes. Let's assume an
<literal>ActionHandler</literal>
interface representing an operation in an application, where some
implementations of an action handler require setup and others do not. Instead of requiring all classes
that implement <literal>ActionHandler</literal> to implement
a method <literal>setUp()</literal>,
an attribute can be used. One benefit
of this approach is that we can use the attribute several times.
</para>
<example>
<title>Implementing optional methods of an interface with Attributes</title>
<programlisting role="php">
<![CDATA[
<?php
interface ActionHandler
{
public function execute();
}
#[Attribute]
class SetUp {}
class CopyFile implements ActionHandler
{
public string $fileName;
public string $targetDirectory;
#[SetUp]
public function fileExists()
{
if (!file_exists($this->fileName)) {
throw new RuntimeException("File does not exist");
}
}
#[SetUp]
public function targetDirectoryExists()
{
if (!file_exists($this->targetDirectory)) {
mkdir($this->targetDirectory);
} elseif (!is_dir($this->targetDirectory)) {
throw new RuntimeException("Target directory $this->targetDirectory is not a directory");
}
}
public function execute()
{
copy($this->fileName, $this->targetDirectory . '/' . basename($this->fileName));
}
}
function executeAction(ActionHandler $actionHandler)
{
$reflection = new ReflectionObject($actionHandler);
foreach ($reflection->getMethods() as $method) {
$attributes = $method->getAttributes(SetUp::class);
if (count($attributes) > 0) {
$methodName = $method->getName();
$actionHandler->$methodName();
}
}
$actionHandler->execute();
}
$copyAction = new CopyFile();
$copyAction->fileName = "/tmp/foo.jpg";
$copyAction->targetDirectory = "/home/user";
executeAction($copyAction);
]]>
</programlisting>
</example>
</sect1>
<sect1 xml:id="language.attributes.syntax">
<title>Attribute syntax</title>
<para>
There are several parts to the attributes syntax. First, an attribute
declaration is always enclosed with a starting
<literal>#[</literal> and a corresponding ending
<literal>]</literal>. Inside, one or many attributes are listed,
separated by comma. The attribute name is an unqualified, qualified
or fully-qualified name as described in <link linkend="language.namespaces.basics">Using Namespaces Basics</link>.
Arguments to the attribute are optional, but are enclosed in the usual parenthesis <literal>()</literal>.
Arguments to attributes can only be literal values or constant expressions. Both positional and
named arguments syntax can be used.
</para>
<para>
Attribute names and their arguments are resolved to a class and the arguments are passed to its constructor,
when an instance of the attribute is requested through the Reflection API. As such
a class should be introduced for each attribute.
</para>
<example>
<title>Attribute Syntax</title>
<programlisting role="php">
<![CDATA[
<?php
// a.php
namespace MyExample;
use Attribute;
#[Attribute]
class MyAttribute
{
const VALUE = 'value';
private $value;
public function __construct($value = null)
{
$this->value = $value;
}
}
// b.php
namespace Another;
use MyExample\MyAttribute;
#[MyAttribute]
#[\MyExample\MyAttribute]
#[MyAttribute(1234)]
#[MyAttribute(value: 1234)]
#[MyAttribute(MyAttribute::VALUE)]
#[MyAttribute(array("key" => "value"))]
#[MyAttribute(100 + 200)]
class Thing
{
}
#[MyAttribute(1234), MyAttribute(5678)]
class AnotherThing
{
}
]]>
</programlisting>
</example>
</sect1>
<sect1 xml:id="language.attributes.reflection">
<title>Reading Attributes with the Reflection API</title>
<para>
To access attributes from classes, methods, functions, parameters, properties and class constants,
the Reflection API provides the method <function>getAttributes</function> on each of the corresponding
Reflection objects. This method returns an array of <classname>ReflectionAttribute</classname> instances
that can be queried for attribute name, arguments and to instantiate an instance of the represented attribute.
</para>
<para>
This separation of reflected attribute representation from actual instance increases control of the programmer
to handle errors regarding missing attribute classes, mistyped or missing arguments. Only after
calling <function>ReflectionAttribute::newInstance</function>, objects of the attribute class are instantiated and the correct matching of arguments
is validated, not earlier.
</para>
<example>
<title>Reading Attributes using Reflection API</title>
<programlisting role="php">
<![CDATA[
<?php
#[Attribute]
class MyAttribute
{
public $value;
public function __construct($value)
{
$this->value = $value;
}
}
#[MyAttribute(value: 1234)]
class Thing
{
}
function dumpAttributeData($reflection) {
$attributes = $reflection->getAttributes();
foreach ($attributes as $attribute) {
var_dump($attribute->getName());
var_dump($attribute->getArguments());
var_dump($attribute->newInstance());
}
}
dumpAttributeData(new ReflectionClass(Thing::class));
/*
string(11) "MyAttribute"
array(1) {
["value"]=>
int(1234)
}
object(MyAttribute)#3 (1) {
["value"]=>
int(1234)
}
*/
]]>
</programlisting>
</example>
<para>
Instead of iterating all attributes on the reflection instance, only those
of a particular attribute class can be
retrieved by passing the searched attribute class name as argument.
</para>
<example>
<title>Reading Specific Attributes using Reflection API</title>
<programlisting role="php">
<![CDATA[
<?php
function dumpMyAttributeData($reflection) {
$attributes = $reflection->getAttributes(MyAttribute::class);
foreach ($attributes as $attribute) {
var_dump($attribute->getName());
var_dump($attribute->getArguments());
var_dump($attribute->newInstance());
}
}
dumpMyAttributeData(new ReflectionClass(Thing::class));
]]>
</programlisting>
</example>
</sect1>
<sect1 xml:id="language.attributes.classes">
<title>Declaring Attribute Classes</title>
<para>
While not strictly required it is recommended to create an actual class for every attribute.
In the most simple case only an empty class is needed with the <literal>#[Attribute]</literal> attribute declared
that can be imported from the global namespace with a use statement.
</para>
<example>
<title>Simple Attribute Class</title>
<programlisting role="php">
<![CDATA[
<?php
namespace Example;
use Attribute;
#[Attribute]
class MyAttribute
{
}
]]>
</programlisting>
</example>
<para>
To restrict the type of declaration an attribute can be assigned to, a bitmask can be passed as the first
argument to the <literal>#[Attribute]</literal> declaration.
</para>
<example>
<title>Using target specification to restrict where attributes can be used</title>
<programlisting role="php">
<![CDATA[
<?php
namespace Example;
use Attribute;
#[Attribute(Attribute::TARGET_METHOD | Attribute::TARGET_FUNCTION)]
class MyAttribute
{
}
]]>
</programlisting>
<para>
Declaring <classname>MyAttribute</classname> on another type will now throw an exception during
the call to <function>ReflectionAttribute::newInstance</function>
</para>
</example>
<para>The following targets can be specified:</para>
<simplelist>
<member><constant>Attribute::TARGET_CLASS</constant></member>
<member><constant>Attribute::TARGET_FUNCTION</constant></member>
<member><constant>Attribute::TARGET_METHOD</constant></member>
<member><constant>Attribute::TARGET_PROPERTY</constant></member>
<member><constant>Attribute::TARGET_CLASS_CONSTANT</constant></member>
<member><constant>Attribute::TARGET_PARAMETER</constant></member>
<member><constant>Attribute::TARGET_ALL</constant></member>
</simplelist>
<para>
By default an attribute can only be used once per declaration. If the attribute should be repeatable on declarations it must
be specified as part of the bitmask to the <literal>#[Attribute]</literal> declaration.
</para>
<example>
<title>Using IS_REPEATABLE to allow attribute on a declaration multiple times</title>
<programlisting role="php">
<![CDATA[
<?php
namespace Example;
use Attribute;
#[Attribute(Attribute::TARGET_METHOD | Attribute::TARGET_FUNCTION | Attribute::IS_REPEATABLE)]
class MyAttribute
{
}
]]>
</programlisting>
</example>
</sect1>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"~/.phpdoc/manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->
|