Skip to content

Special characters in payload are not parsed properly #42

Answered by enisdenjo
jbanulso asked this question in Q&A
Discussion options

You must be logged in to vote

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": "á, é, í, ó, ú, ñ"
      }
    }
  }
}

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@jbanulso
Comment options

Answer selected by jbanulso
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #41 on December 20, 2022 14:11.