Nico Rehwaldt

> My understanding is that for `zeebe:input` and `zeebe:output` properties of type boolean and number we need to enforce `"feel": "static"` and cannot make it optional. Am I right? Yes....

Thanks for the PR! It allowed me to investigate this issue. I checked what `eslint-astro-parser` generates as a syntax tree, parsing the source code file you provided: ``` --- const...

This shows a limitation of our existing architecture: We can only access (and save) the contents [of the currently opened tab](https://github.com/camunda/camunda-modeler/blob/c612b7eb81eb4b2321c7b2278224781419d9a7b6/client/src/app/App.js#L1446). As a result save on blur in this proposal...

@copilot Can you change the [tab saving implementation](https://github.com/camunda/camunda-modeler/blob/c612b7eb81eb4b2321c7b2278224781419d9a7b6/client/src/app/App.js#L1446) so it happens independent from the currently opened tab?

> We cannot save all related files before deploying a process application. And this exactly is the reason why we want to embrace auto-safe, so things are "saved per default",...

This PR is ready for "functionality preview", I ask you to have a look and see if it meets our performance criteria. The core implementation is solid, I believe. However...

Challenge to overcome here: Secrets are only supported in _some_ places, i.e. only in connectors or potentially other workers that support them. We could decide to _always_ recognize the pattern...

@barmac I'm not sure if we understand the grammar in the same way, to me it says: ``` 33. string literal = """, { character – (""" | vertical space)...

@barmac Let's consider to close this issue ("wont fix, works as specified") or at the very least update the issue title and description. I think it is still misleading.

> If we are not supporting linebreaks in a user friendly way, the system prompts are becoming unreadable. @bastiankoerber that is a mis-understanding. Of course they support line breaks in...