We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When decoding a json to object, it added escape to string based value.
{"id":"5f0bcaa46e0ba209eb68f47b","body":"test","sentAt":"2020-07-13T02:44:52.628Z"}
{"id":"5f0bcaa46e0ba209eb68f47b","body":"\"test\"","sentAt":"2020-07-13T02:44:52.628Z"}
I have written a sample which is help for reproducing this issue.
https://github.com/hantsy/angular-spring-rsocket-sample
Update: when I perform a query on the Mongo server, it shows.
> db.messages.find(); { "_id" : ObjectId("5f1564db0a7da37b085e8bd7"), "body" : "test", "sentAt" : ISODate("2020-07-20T09:33:15.527Z"), "_class" : "com.example.demo.Message" } { "_id" : ObjectId("5f15650a0a7da37b085e8bd8"), "body" : "\"hello rsocket\"", "sentAt" : ISODate("2020-07-20T09:34:02.042Z"), "_class" : "com.example.demo.Message" } { "_id" : ObjectId("5f1565140a7da37b085e8bd9"), "body" : "\"yeah, finally works\"", "sentAt" : ISODate("2020-07-20T09:34:12.453Z"), "_class" : "com.example.demo.Message" }
Does this mean when the server received the message from the client, the JSON serializer added a slash to escape the string?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When decoding a json to object, it added escape to string based value.
Expected Behavior
Actual Behavior
Steps to Reproduce
I have written a sample which is help for reproducing this issue.
https://github.com/hantsy/angular-spring-rsocket-sample
Update: when I perform a query on the Mongo server, it shows.
Does this mean when the server received the message from the client, the JSON serializer added a slash to escape the string?
The text was updated successfully, but these errors were encountered: