Maciej Barelkowski
Maciej Barelkowski
I can reproduce it in 5.34, so it's not a regression.
The template property field `feel: static` means that no FEEL editor is displayed to the user. So the parser dialect is irrelevant in that case. Please read the templates documentation...
What do you think we should do?
Why would an element template specify the parser dialect? Please consider that element templates are just a frontend to specify BPMN + Camunda-specific properties. The expressions are evaluated mostly by...
Indeed the idea is to configure this for the entire properties panel when the Zeebe provider is used. So the element templates should pick it up automatically.
> [@nikku](https://github.com/nikku) [@barmac](https://github.com/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...
@Buckwich I just noticed that `feel-lint@2` was never adopted in [the feel-editor](https://github.com/bpmn-io/feel-editor/blob/main/package.json#L48). Any plans to migrate?
Not sure if this is urgent, but at least you remember the context right now. The migration might be more troublesome a month from today.
I've tried to reproduce this now with a paused `Camunda 8.7+gen5` cluster. This time, I received an `Error: 14 UNAVAILABLE: Received HTTP status code 502` error. The token was fetched...
Done via https://camunda.slack.com/archives/C08MRKHJ0CD/p1751273416517549