Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Behavior When Switching between FEEL and Non-FEEL Property #3075

Closed
GeethaParthasarathy opened this issue Aug 5, 2022 · 1 comment

Comments

@GeethaParthasarathy
Copy link

GeethaParthasarathy commented Aug 5, 2022

Problem you would like to solve

  1. Select a field where the FEEL expression is not mandatory
  2. Fill in the field with any expression in the Feel
  3. Try to switch between normal text field and the Feel editor
  4. Now in the normal text field try to edit the expression
  5. Switch back to feel editor
  6. We could see that the new line formatting is not maintained when we switch between normal text field and feel editor

Proposed solution

We should clarify the behavior regarding formatting and preserving whitespace characters when switching between FEEL and non-FEEL properties. Right now, the behavior feels broken.

Alternatives considered

  • be explicit and remove line breaks when switching from FEEL to non-FEEL - single line means single line

Additional context

align_editors.mp4
@GeethaParthasarathy GeethaParthasarathy added the enhancement New feature or request label Aug 5, 2022
@philippfromme philippfromme changed the title Improve the formatting of the text when we edit and switch between Feel editor and a normal text field Clarify Behavior When Switching between FEEL and Non-FEEL Property Aug 5, 2022
@pinussilvestrus pinussilvestrus added the backlog Queued in backlog label Aug 22, 2022 — with bpmn-io-tasks
@nikku
Copy link
Member

nikku commented Sep 30, 2024

I reviewed this one again. Once you edit the (single line) text then the (FEEL) newline information is gone. It still works if you just (accidentally) toggled, toggling FEEL back on keeps the newlines:

capture tWNBSj_optimized

For this reason I regard this as an edge case, and will close this issue.

@nikku nikku closed this as not planned Won't fix, can't repro, duplicate, stale Sep 30, 2024
@bpmn-io-tasks bpmn-io-tasks bot removed the backlog Queued in backlog label Sep 30, 2024
@nikku nikku removed the spring cleaning Could be cleaned up one day label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants