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
New lines written as "\n" cause database to response with "Parse error".
What's weird is that even sending "\n" it will still throw same error.
Only sending new line as real new line (pressing enter) will be accepted.
Problem is pretty annoying while sending JSON data from JS sdk.
Steps to reproduce
Command that will throw error: CREATE test SET value = "sometext\nwithnewline"; CREATE test SET value = "sometext\\nwithnewline";
Expected behaviour
Save values with "\n" as text, allow to unescape it or just parse it as new line.
SurrealDB version
v1.0.0-beta.7 for linux amd64
Contact Details
No response
Is there an existing issue for this?
I have searched the existing issues
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
New lines written as "\n" cause database to response with "Parse error".
What's weird is that even sending "\n" it will still throw same error.
Only sending new line as real new line (pressing enter) will be accepted.
Problem is pretty annoying while sending JSON data from JS sdk.
Steps to reproduce
Command that will throw error:
CREATE test SET value = "sometext\nwithnewline"; CREATE test SET value = "sometext\\nwithnewline";
Expected behaviour
Save values with "\n" as text, allow to unescape it or just parse it as new line.
SurrealDB version
v1.0.0-beta.7 for linux amd64
Contact Details
No response
Is there an existing issue for this?
Code of Conduct
The text was updated successfully, but these errors were encountered: