Btw.: there are late discussions in regards to integrating the properties panel into an Angular application: Error while using bpmn-js-properties-panel and camunda-bpmn-moddle in angular10 application. Did you already read through those threads?
I’ve read through it on an earlier occasion, but it’s not relevant to my case now. My angular app does allow importing json modules. You can confirm that by checking out the tsconfig.json in the codesandbox.
I have cleaned up the codesandbox code a little, to make it more readable.
where do you define the container for the Modeler and the Properties Panel?
The containers are defined in the lines immediately after declaring the class:
@ViewChild("diagramContainer", { static: true }) private diagramContainer: ElementRef;
@ViewChild("propertiesPanelContainer", { static: true }) private propertiesPanelContainer: ElementRef;
Codesandbox forces the new line before “private”.
The modeler is attached in the ngAfterViewContentInit():
this.bpmnJS.attachTo(this.diagramContainer.nativeElement);
The Properties Panel is not being attached yet, because the app begins crashing as soon as I uncomment the lines:
// additionalModules: [propertiesPanelModule, propertiesProviderModule],
// moddleExtensions: {
// camunda: camundaModdleDescriptor
// }
This error, which I’ve quoted in my post above, is the problem that I am experiencing only on codesandbox, and it prevents me from demonstrating my actual issue to you - “Cannot read property ‘depends’ of undefined”.
You can reproduce it by uncommenting the four lines I’ve quoted just above this paragraph. I have to work around this error before I can demonstrate the issue with the Properties Panel not updating its Extensions tab to display the custom properties of a drag&dropp-ed user task.