Alternative Description architecture

[dantleech]

We could use objects for the Descriptors and access them by their class name:

$description->addDescriptor(new HtmlLinksDiscriptor([
    HtmlLinksDescriptor::EDIT => '/path/to/edit/1',
    HtmlLinksDescriptor::REMOVE => '/path/to/remove/1',
    // ...
]);

$description->addDescriptor(new ChildClassesDescriptor([
     FooClass::class,
     BarClass::class
]);


$linkUrl = $description->getDescriptor(HtmlLinksDescriptor::class)->getEditUrl();

if ($description->hasDescriptor(ChildClassesDescriptor::class)) {
    $childClasses = $description->getDescriptor(ChildClassesDescriptor::class)->getChildClasses();
}

It can then be assumed that if the client is requesting the descriptor by class name, that they know what to do with it (i.e. it can have its own public API).

Unfortunately this is very verbose in Twig:

<h1>Hello</h1>
<a href="{{ description.hasDescriptor('Name\Space\Descriptor\HtmlLinksDescriptor') ? description.descriptor('Name\Space\Descriptor\HtmlLinksDescriptor').editLink }}">Edit</a>

This approach solves the current ambiguity problem posed by having a simple key/value store, but increases the verbosity, especially in Twig and when consumed through the REST service.