-
Notifications
You must be signed in to change notification settings - Fork 173
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
feat: Chat Web API (now with no threading) #1715
Conversation
add all previous POC api endpoints
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.
questions and some ways to consider designing where the logic is handled
we should chat about what I think would be an easier to read message handler for the webapi server (moving the actual logic to the places that own it, and only using the handler to receive, figure out where it goes, and return a result
Co-authored-by: David Markowitz <[email protected]>
Co-authored-by: David Markowitz <[email protected]>
Co-authored-by: David Markowitz <[email protected]>
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.
Some comments, nothing blocking.
Co-authored-by: Daniel Seiler <[email protected]>
my commit isnt a merge commit, forgot to rename it |
re-working some stuff |
I worked on this so I cannot approve this technically |
using mongoose for the http lib
Web API for Chat server Minimum Viable Product
Features:
resolves #450