-
Notifications
You must be signed in to change notification settings - Fork 2
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
Instant messaging with WebSocket #344
Conversation
use uvicorn instead of daphne to run asgi backend app so it can be hot-reloaded on dev environment
- change in database models for conversations, messages, and conversation participants - api endpoints for conversation related information - api endpoint for user's conversation at `/accounts/{accountID}/conversations` - tests for said endpoints
- setup websocket for messaging system - receiving messages from the server to clients in real-time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left a few comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you update dependencies? i have never seen this view in github before kinda cool. I will approve for now but shotoh had good questions about the exceptions.
[Backend]
/conversations
(create conversations, get conversation messages, and get users/accounts' conversations)[DevOps]
uvicorn
fromdaphne
to run the backend ASGI app for hot-reloading (see [DevOps] Improve hot reloading for Django Channels with Docker #336)