Update WebSocket API and enhance message retrieval features #10
Conversation
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
Contributor
LifeRIP
commented
Jun 10, 2025
LifeRIP
commented
- Require Firebase Auth Token in WebSocket connections, revise message ordering, and introduce pagination for room messages.
- Enhance message responses to include user display names and add support for both paginated and non-paginated message retrieval.
- Update API documentation accordingly.
feat: Update WebSocket API to require Firebase Auth Token in the query params URL
Changes message ordering from descending to ascending in room and direct chat repositories to align with updated requirements. Removes the 'before' query parameter from API documentation as it is no longer supported.
Refactor message ordering and update API documentation
- Introduces a new `MessageResponse` type to include user display names alongside messages. - Updates retrieval methods for room and direct chat messages to fetch user data and enhance responses.
- Updates the Air configuration to enable polling and sets the poll interval to 1000ms. This change likely improves file monitoring or responsiveness in development workflows in Windows.
- Enhances the GetRoomMessages functionality by introducing pagination support with descending order based on creation date. - Updates API specifications to include a cursor for pagination and returns a structured response containing paginated messages, next cursor, and a flag for more data availability. - Refactors repository logic to handle pagination, including timestamp-based cursors.
- Introduces a new endpoint for retrieving room messages without pagination, allowing clients to specify a limit. - Updates routing to differentiate between paginated and non-paginated message retrieval.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.