Better documentation #108
SteelDrEgg
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
It’s already in the plan. Right now the developer is busy with the “job” that pays $2000 a month 😶🌫️. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is one of the best implementations of Socket.io in GoLang, but a better documentation could help more people to get started.
Some code in the README isn't plug and play; either the API has changed, or it's just pseudocode.
Most of the useful informations are hidden in the source code, test file, or discussions. It would be great if we could have a separate documentation with open box examples to play around with.
If the team is busy working to the code, I think it would be a good idea to be open with documentation PRs and let the community collectively improve it.
Beta Was this translation helpful? Give feedback.
All reactions