Adaptive size of the documentation text box

[ingorichtsmeier]

Problem you would like to solve

Having a huge documentation text, I can increase the size of the textbox to see all at once.

When I select another element and coming back to the one with the huge documentation, the box shrinks again to the default size.

Proposed solution

• The textbox for Documentation should remember its size after increasing for all elements.
• We want to persist that information across modeler sessions (i.e. in persisted layout configuration)

Alternatives considered

Show everything by default.

But this could be distracting for users that don't care about the complete documentation and are only interested if a documentation exists or not.

Additional context

The diagram converter from https://github.com/camunda-community-hub/camunda-7-to-8-migration generates all migrations into the documentation element.

Depending on the Camunda 7 element configuration and element content, it could become many characters and sentences.

[nikku]

@ingorichtsmeier Could you share a screenshot of the migration text generated and attach it to the issue?

I guess what you envision is something like what we have with the FEEL editor, right?

[ingorichtsmeier]

Not exactly.

Here is a screenshot:

I could not show everything, because it contains sensitive information. But the size of the scroll bar shows how long it can become.

I think it is OK to save the new size of the textbox and apply it to all other BPMN elements. They usually have different content and I have chosen the largest.

[nikku]

The textbox for Documentation should remember its size after increasing for all elements.

We cannot remember across sessions, but we may be able to remember within an individual session.

[ingorichtsmeier]

What about adding the size to config.json on disk?

I found this file in AppData\Roaming\camunda-modeler even touched today without using the modeler. It's still running in background.

[nikku]

What about adding the size to config.json on disk?

That is a away to persist it. Good idea. I updated the issue accordingly.

[vishalsingh2972]

@nikku can you assign this to me, want to give this a try!

[nikku]

Happy to take your contribution in the form of a PR. We don't usually assign external contributors.

[barmac]

We already have it in the name field of the BPMN editor.

[jarekdanielak]

Fixed upstream by bpmn-io/properties-panel#377