search

valb3r / flowable-bpmn-intellij-plugin

Flowable, Activiti, Camunda BPMN engines process editor plugin for IntelliJ. Pure Kotlin (and some Java)
https://plugins.jetbrains.com/plugin/14318-flowable-bpmn-visualizer
MIT License
157 stars 31 forks source link

Flowable- scripttask - code reformated #311

Open mindstorm-r opened 2 years ago

mindstorm-r commented 2 years ago

Describe the bug A clear and concise description of what the bug is.

During development of workflow we need add new components and move otherone . If component - scrpittask contains inside code (groovy) formated and we move it on designer to other place, or add other component on designer , the code is being reformated to one line .

To Reproduce Steps to reproduce the behavior:

  1. Create workflow with components - scripttasks
  2. Provide conde in scripttasks , format it properlly
  3. Move scripttask to other place on designer or add new component on designer.
  4. You will se formated code to one line.

Expected behavior Code should not change during moving components on designer.

IntelliJ version (please complete the following information):

FLowable plugin version:

valb3r commented 2 years ago

@mindstorm-r Thanks for feedback, but it we are unable to reproduce the issue. Can you provide more details - OS, animated GIF of your steps

mindstorm-r commented 2 years ago

@mindstorm-r Thanks for feedback, but it we are unable to reproduce the issue. Can you provide more details - OS, animated GIF of your steps

Hi,

I am sorry but it happening constantly. All my team have that problem. One thing what i can add is that the workflow needs to have couple of components. Workflow can not be small. It happening no matter wih verions of intellij i use .

valb3r commented 2 years ago

@mindstorm-r Please provide:

  1. IntelliJ version
  2. OS type and version
  3. Example file where the issue happens
  4. Ideally GIF with the issue happening on screen

This will greatly reduce time for spotting the root cause, as it might be a combination of i.e. return characters/tabs and their default treatment by parser, currently we are unable to reproduce the issue on MacOS and Windows with spaces and '\n'