Nico Rehwaldt
Nico Rehwaldt
I've shared the following on the original slack converstation: > Core modeling tooling tries to be a little bit less cursory / flashy for interactive elements to be agnostic where...
Thanks for the report, I can reproduce this issue.
Alternative: Have a "wrap in sub-process" refactoring action.
> > Alternative: Have a "wrap in sub-process" refactoring action. > > As a multi-element selection context pad action, right? In whatever way we deem necessary. Given the fact that...
@mnp-mid You mention the one benefit of this change: "folks used to ES6 (classes only) code base) can navigate the source code better". On the flip side the transformation will...
> TypeScript is already partially settled in this project, so considering using classes would bring you closer to use TypeScript, which has better support for types and refactoring. This is...
> the main benefit will be in the reduced bundle size. Which is negated as soon as you GZIP things.
CC @nithinssabu
I agree this can be a valuable feature. We just have to decide if we want to disable it all together (I don't think so), or give users control whether...
Came up again in [this conversation](https://camunda.slack.com/archives/C0693F1NFK5/p1728463367024459).