You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah, update functionlity is difficult and may need custom logic per template. And as such, update functionality still is problematic on many levels. Will keep this here as a reminder for future updates.
If using the textarea field type and json dataformat, newlines are parsed differently depending on if play or update command is used.
Template definition:
Example input:
![image](https://user-images.githubusercontent.com/7373055/195802669-66014740-57d7-43d4-83a7-feac3833b4e8.png)
Value of f0 when using play:
Test test test<br>Second line test
Value of f0 when using update:
Test test test\nSecond line test
So on play(), the newline is converted to an escaped
<br>
tag, which seems to be happening here: https://github.com/TuomoKu/SPX-GC/blob/master/routes/routes-application.js#L1359-L1372But for some reason, the same is not done on update(). This makes it hard to code template logic that detects newlines.
The text was updated successfully, but these errors were encountered: