Hey Luuk!
Thanks again for the quick reply!
I’ve tested out your logic, and it works great… but unfortunately not when the custom property editor exists on a document type that is added via a Block List.
It just doesn’t seem to run the following at all.
this.consumeContext(UMB_CONTENT_WORKSPACE_CONTEXT, (instance) => {
console.log("Instance", instance);
this.observe(instance.structure.contentTypeAliases, (aliases) => {
console.log("Aliases", aliases);
});
});
It’s given me an idea of where I would typically find the aliases for the document type, so that’s a step in the right direction for me.
I wonder if I am supposed to be able to consume the content workspace context from inside of the block list modal.
Thank you,
Rob