- Issue created by @DamienMcKenna
- Status changed to Needs review
12 months ago 4:22pm 7 December 2023 - πΊπΈUnited States jrockowitz Brooklyn, NY
Via the latest release, you can go to /admin/config/schemadotorg/settings/jsonld and tweak 'Schema.org type entity references display'
- πΊπΈUnited States DamienMcKenna NH, USA
If I have a field "author" that points to a vocabulary "Person" and I want to output a "Person" object, would I write it like this?
taxonomy_term--Person: Person
The syntax of these fields is not clear - should it be like this?
[entitytype]--[bundle]: [data type]
If so, why does the example use an uppercase first character for the bundle name? - πΊπΈUnited States jrockowitz Brooklyn, NY
If so, why does the example use an uppercase first character for the bundle name?
It can be the bundle name (person) or the Schema.org type (Person).
- πΊπΈUnited States jrockowitz Brooklyn, NY
You might want to try
taxonomy_term: entity
- πΊπΈUnited States jrockowitz Brooklyn, NY
I think we might want to default to rendering all mapped taxonomy terms.
Does the MR work as expected?
- Merge request !86Issue #3406814: How to render reference field as complex object β (Merged) created by jrockowitz
- Assigned to DamienMcKenna
- πΊπΈUnited States DamienMcKenna NH, USA
I installed the taxonomy submodule and then was able to define some elements on the vocabulary's schema definition, and I'm able to make it work the way I need.
I think the patch would help for better defaults, but I think some documentation will help too. I'll work on that next week.
- πΊπΈUnited States jrockowitz Brooklyn, NY
@DamienMcKenna I definitely need help with the documentation and the overall documentation strategy for the module.
- πΊπΈUnited States jrockowitz Brooklyn, NY
I am going to merge the change AS-IS and we can improve the documentation as needed.
-
jrockowitz β
committed 5fb107ff on 1.0.x
Issue #3406814: How to render reference field as complex object
-
jrockowitz β
committed 5fb107ff on 1.0.x
- Status changed to Fixed
8 months ago 11:51am 24 March 2024 - Issue was unassigned.
Automatically closed - issue fixed for 2 weeks with no activity.