The common custom-section resolver: load the queried object and, when it is an instance of the
given type, answer with the path the plugin's section shows it under.
Sections built with TypeSection.createTypeSectionExtension never need a resolver — their url
binding ends in the typename, which is all plugin-space's generic section lookup needs. This is
for sections with a shape of their own (a virtual grouping node, a section id where the typename
would be), whose objects the generic resolvers can only place in the database subtree.
The common custom-section resolver: load the queried object and, when it is an instance of the given type, answer with the path the plugin's section shows it under.
Sections built with
TypeSection.createTypeSectionExtensionnever need a resolver — their url binding ends in the typename, which is all plugin-space's generic section lookup needs. This is for sections with a shape of their own (a virtual grouping node, a section id where the typename would be), whose objects the generic resolvers can only place in the database subtree.