Add schema-class-specific UI components #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When a user currently selects a class in the left-hand-side pane, all known instances of that class are shown, such as in the attached screenshot.
The current display of such a "card" is generic. The original and continued idea for
shacl-vueis to dynamically render forms (editors) AND object displays (viewers) based on the specifics of the nodeshape and propertyshape being assessed. So just likeshacl-vuehas node-and-property-shape specific components that are dynamically matched and rendered in forms, it can have specific components that are dynamically matched and rendered in displays such as the current generic list of cards.We can start with a display for a
Thing, since that would be the most generic and also default/fallback display component. And then additional components can be built for more speciallized classes. And these components can be included/excluded, i.e. become part of the pool of matchable components, on a per-deployment basis.