Nico Rehwaldt

@pablocabrera85 You closed this issue as not planned, is that correct? Your comments indicate that the things are fixed. Did we fix it, or put it to backlog? If we...

I changed this issue to _closed as completed_ and linked the PRs "closing" it, specifically https://github.com/camunda/camunda-docs/pull/6473. Thanks ⭐

@pablocabrera85 one question: Did we include redirects in our restructuring? I visited [this page](https://docs.camunda.io/docs/next/components/modeler/desktop-modeler/element-templates/defining-templates/) and it is now broken.

This can in principal be integrated on top of https://github.com/camunda/camunda-bpmn-js/pull/393.

Thanks for the update. I guess we could even provide this as a plug-in and see if it is an improvement. The first one is covered by our existing search...

I linked this to additional https://github.com/camunda/camunda-modeler/issues/4809, the initiative that would need it.

> Clarified with barmac: My current approach was to set the parserDialect in each [input in bpmn-js-properties-panel individually](https://github.com/bpmn-io/bpmn-js-properties-panel/commit/c7a11dd820a8883e58374e22e1282e3c8372c23c), better would be to generalistic default to parserDialect:'camunda' To add to that...

@Buckwich can you update this regarding the work left?

Not sure were we teased type declarations for dmn-js. It surely is something we want to work on, some day, maybe. Moving to backlog for the moment.

@BrianJVarley I understand that this is not 100% convenient to not have it in dmn-js (yet). There exists [ways for you to work around](https://medium.com/@steveruiz/using-a-javascript-library-without-type-declarations-in-a-typescript-project-3643490015f3), i.e. by creating your own declaration...