Improve Entity display
Within ITI use-cases there seems to be a need for a middle ground between the basic EntityItem with just Entity.label
and a fully implemented EntityType-specific EntityItem: a EntityItem containing a link/url that would point to an external site where the Entity is further described.
I imagine an implementation to change the part where the used EntityItem i decided to work as follows:
- Check
Entity.types
array for matches for a custom type-specific EntityItem Component - If nothing was found, check if
Entity.details
optional property exists. If it exists, useDetailsAwareEntityItem
(name tbd) that then could itself check for availability ofdetails.url
ordetails.description
and other supported properties and handle them. - If no details were provided, use current
EntityItem
component
This keeps the Entity schema clean and unchanged and lets the current EntityItem
component be as primitive as it is while allowing for additional likely props without the need to create many additional EntityTypes.
It would also enable access to extensive Entity details where in-application display (and thus a custom type-specific EntityItem) is not needed.
Edited by Mittermeier, Maximilian