FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Client emit or send, nothing cames to server #790 by marktech0813 · Pull Request #792 · socketio/socket.io-client-java · GitHub

Client emit or send, nothing cames to server #790 - #792

Open
marktech0813 wants to merge 2 commits into
socketio:mainfrom
marktech0813:develop
Open

Client emit or send, nothing cames to server #790#792
marktech0813 wants to merge 2 commits into
socketio:mainfrom
marktech0813:develop

Conversation

Copy link
Copy Markdown

I added a defensive improvement and documentation to address your issue.

  • In Socket.emit(...), the client now logs a warning if you emit a JSON-looking string (e.g., "{...}" or "[...]"), prompting you to send a JSONObject/JSONArray instead.
  • In src/site/markdown/emitting_events.md, I documented this pitfall with a “wrong vs correct” example.

I added a defensive improvement and documentation to address your issue.

In Socket.emit(...), the client now logs a warning if you emit a JSON-looking string (e.g., "{...}" or "[...]"), prompting you to send a JSONObject/JSONArray instead.

In src/site/markdown/emitting_events.md, I documented this pitfall with a “wrong vs correct” example.
In src/site/markdown/emitting_events.md, I documented this pitfall with a “wrong vs correct” example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant


Back | FazBrowse Home | New Git URL