You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I have yet to find a way to set the "hydra:title" of my property. I am planning to use hydra:title as table header in dynamic tables, this is what this kind of usage that property was meant for.
I tried overriding the context to no avail:
jsonldContext: [
'hydra:title' => 'Name'
])
Being able to override the name and description should be equally easy to my understanding, when reading the Hydra Core Vocabulary spec:
Hydra also allows enriching both ApiDocumentation and hypermedia controls with human-readable descriptions by applying title and description (as shown in the examples above). The former states a name of such a decorated element that could be displayed as a label. The latter provides its description to be presented i.e. as a hint.
Aforementioned title and description SHOULD take precedence over standard rdfs:label and rdfs:comment.
Example
Proposed implementation:
#[ApiProperty(
description: 'Name of the product',
title: 'The name'
]
private ?string $name = null;
Description
Currently, it is very easy to add a description to an entity's field:
And it gets reflected in the /api/docs.jsonld:
However, I have yet to find a way to set the "hydra:title" of my property. I am planning to use
hydra:title
as table header in dynamic tables, this is what this kind of usage that property was meant for.I tried overriding the context to no avail:
Being able to override the name and description should be equally easy to my understanding, when reading the Hydra Core Vocabulary spec:
Example
Proposed implementation:
Would produce:
The text was updated successfully, but these errors were encountered: