I think I may have imagined a feature because I can't find it in the documentation.
Is it possible to have a context app, where it shows the editor for a single entity rather than the list view of a collection?
Additionally can you have a context app where the FK is held within the content, rather than the entity having the FK?
My use case being:
A collection of Resources is already setup in Konstrukt
A user creates a ResourcePage in the content section
A property on the ResourcePage has uses an Entity Picker to allow selection of a Resource (the content is then published).
A Content App exists for the ResourcePage that shows the Editor view of the resource that was picked on the content item.
I'm guessing I'm making stuff up đł.
The open button in the Entity Picker is a good fallback to create the sort of UX that I'm imagining. Even better would be if the Editor could load an overlay so that they don't need to leave the content section to edit a mixture of content and custom data tables.
Unfortunately no you canât do that. Konstrukt is always âcollectionâ based so youâll always have a list view and then an editor view.
Re linking on something other than the entity ID again unfortunately not. I think we do have an ID resolver that can be replaced but that still assumes itâll be a node ID
Displaying an editor in a context app
I think I may have imagined a feature because I can't find it in the documentation.
Is it possible to have a context app, where it shows the editor for a single entity rather than the list view of a collection?
Additionally can you have a context app where the FK is held within the content, rather than the entity having the FK?
My use case being:
Resources is already setup in KonstruktResourcePagein the content sectionResourcePagehas uses an Entity Picker to allow selection of aResource(the content is then published).ResourcePagethat shows the Editor view of the resource that was picked on the content item.I'm guessing I'm making stuff up đł.
The open button in the Entity Picker is a good fallback to create the sort of UX that I'm imagining. Even better would be if the Editor could load an overlay so that they don't need to leave the content section to edit a mixture of content and custom data tables.
Hey David
Unfortunately no you canât do that. Konstrukt is always âcollectionâ based so youâll always have a list view and then an editor view.
Re linking on something other than the entity ID again unfortunately not. I think we do have an ID resolver that can be replaced but that still assumes itâll be a node ID
is working on a reply...