Simon

Here is the deprecation notice from github: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ So @actions/core needs to be updated to v1.10.0

For example [NRWL/NX](https://github.com/nrwl/nx) (a monorepo build system) often uses `schema.json` and `schema.d.ts` in its executors and generators. So I would like to run `json2ts -i './**/schema.json' -m` to make it...

Two ideas to approach this: 1. Direct creation of PRs in other Repos: Con: Requires PAT to write/create PR 2. Trigger other workflows and let them download the artifacts Con:...

I saw in https://github.com/camunda/web-modeler/pull/13911/files#diff-3bb584bc8fb5b86f0c09ab9f652990cd47228c025dfaf25defb0c2f267f28054R291 that they give options to the field eg `feel: static`, should we set the parserDialect for those to camunda as a default or rely on their...

Okay that was a bad example, question is still the same. What if they set `feel: required`? should we default to camunda or just follow what the template provides.

>What do you think we should do? don't change the existing behavior, ie make them explicitly set the parserDialect camunda. But I would raise an issue with the feeleditor autocomplete...

don't they allow to define custom property fields (cf. https://docs.camunda.io/docs/components/modeler/desktop-modeler/element-templates/defining-templates/#defining-template-properties). and that input field could also be a feel expression, my question was if this input field should default to...

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'

only the zeebe properties provider is using the feel editor (in bpmn-js-properties-panel), there I set camunda as default: https://github.com/bpmn-io/bpmn-js-properties-panel/pull/1120 In properties-panel the value is just configurable without a default for...

@nikku @barmac Just to confirm: https://github.com/bpmn-io/dmn-js/pull/943/files is **not** what we want to do for dmn-js, right? But what I don't get is why we suggest camunda methods by default