Open fhsevenbel opened 3 years ago
@fabianhintringer this is a somewhat surprising outcome from a desktop client update; can you try testing if the messages format properly when using 5.7.0? If not, then the explanation is likely a server bug introduced around the same time.
It would also help if you show how you're calling curl (be sure to redact any API tokens). But if you're calling curl directly, that's not going to be affected by the local version of the Zulip Desktop client.
Describe the bug Since the new 5.8.0 update "\n" newlines are not recognized anymore, at least when sending messages via the api.
We posted messages via the
https://zulip_url/api/v1/messages
url to our zulip members With version 5.7.0 everything worked fine like thisBut on version 5.8.0 the newlines are ignored and it is just one really long string
To Reproduce
Try sending a message using curl, containing a newline "\n" to the Zulip API. The newline will not be recognized
Expected behavior
The newline should be recognized and the message should be formatted correctly again
Pre 5.8.0
5.8.0
Desktop (please complete the following information):
Operating System: Our whole team has the same problems, we are using Windows 10 and POP!_OS
Zulip Desktop Version: 5.8.0
Additional context