-
I'm reporting the issue in this repo because after checking our subscriptions implementation across the whole stack here's where the culprit seems to be. Screenshot
Expected Behaviour Actual Behaviour Debug Information Further Information |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The server is most likely not encoding the characters in UTF-8. If I pass those same characters to a subscription resolver, I get them properly decoded on the client: {
"event": "next",
"data": {
"id": "2e3c1aec-3f20-483b-a0ff-0318a767ba38",
"payload": {
"data": {
"chars": "á, é, í, ó, ú, ñ"
}
}
}
} |
Beta Was this translation helpful? Give feedback.
The server is most likely not encoding the characters in UTF-8. If I pass those same characters to a subscription resolver, I get them properly decoded on the client: