If you only need unformatted paragraphs (every newline marks a new paragraph) you may use a long answer input while you wait for the full rich text editor.
You can split the value of the input on newlines:
Then you have an array of strings that you can display with the column element.
It is very basic but quick.
Of course the data structure is different from what you will get from the rich text editor. If you use this workaround now and use the rich text later you may need to change how you store the data in your backend.
Also, in this way you have full control on how to display the paragraphs after editing but you canāt style the value of the input, so during editing it will be just an unstyled text in the input.
Wow thatās a cool workaround! I think you are right that it will be a data structure mess after switching, so I might as well wait at this point. Would be nice to have a preview of the rich text element because if it is very busy (especially on mobile) I may decide to use your method. Thank you!
@kyanaloe, yes, we really messed up on this one. First we ran into a few technical roadblocks in June, then we got our wires crossed during the review process, lacking coordination between summer holidays. Weāre very sorry about this.
Not sure if you were able to attend the live stream last week where we began by addressing this issue. Basically, itās very close to being released but there are a couple of big items that are tied to that release and mean we still canāt commit on an exact date unfortunately.
Again, really sorry about this! We strive to do better.
