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
SignalR automatically can receive objects, and serialize these the JSON or MessagePack.
It is currently not possible to avoid / override this step.
This functionality causes an already JSON serialized string to be serialized again.
This step turns the payload into a JSON String, and not the JSON representation of the object we want to send.
SignalR automatically can receive objects, and serialize these the JSON or MessagePack.
It is currently not possible to avoid / override this step.
This functionality causes an already JSON serialized string to be serialized again.
This step turns the payload into a JSON String, and not the JSON representation of the object we want to send.
Example ref: Is it possible to return a pre-encoded JSON string in a SignalR hub method?
(Yes it is old, but still valid)
Because this whole server is built around the concept of serving any provided json structure, we have no Object representation of the data.
Example:
The current correctly formatted text is passed to the SignalR client
In the payload body it has been serialized again and now looks like this
"{ \"key\":\"value\" }"
This is now a single string, and this causes trouble
The text was updated successfully, but these errors were encountered: