-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
need a real usage example #14
Comments
Hi @kneufeld - what behavior did you encounter when using Additionally, I'm always open to PRs. Since you've found an edge here in terms of usability, you're the best person to propose a change that would ensure others don't run into the same problem that you did. Thanks! |
@Fitblip, I've prepared a real usage example in the description at
|
|
Ok, so it sounds like the real issue here is that we're not erroring out if you specify non-ws protocols (namely When I get time I'll fix it, or if one of you wants to tackle it PRs are always welcome! Also @skamieniarz - you don't have permissions to this repository due to how Github works. If you want to submit a pull request you need to fork this repo and submit a PR from your fork. Thanks! |
I just wasted a good hour because I had
http://localhost:8000/ws
as thewebsocket_url
instead ofws://localhost:8000/ws
. Yes I know that's on me but having usage examples are absolutely key for any project.The text was updated successfully, but these errors were encountered: