feat(frontend): implement collaboration service #14
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
ncduy0303
force-pushed
the
ncduy0303/collaboration-service-frontend
branch
from
4251476 to
0374254
Compare
DanielJames0302
approved these changes
Oct 27, 2025
DanielJames0302
left a comment
DanielJames0302
left a comment
There was a problem hiding this comment.
LGTM ! In the next PR, it should add a function to get the details of the question from the question id along with room details
- Integrate collaboration service backend with into Code Editor panel on /practice/:id pages. - Add placeholder panels for Question, Communication, Code Execution.
ncduy0303
force-pushed
the
ncduy0303/collaboration-service-frontend
branch
from
fce97c5 to
02aaf62
Compare
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.
Description
This PR continues from #8 and replaces #7 to integrate the collaboration service into our frontend.
Screenshots or videos if applicable
Room page (/practice/:room_id)
Add placeholders for Question, Communication, and Code Execution panels. Future PRs should integrate those backend services into the frontend.
Two users collborating in an active room
Integrate collaboration service backend into Code Editor panel:
collab-demo.mp4
Note: "Leave Room" would redirect users back to the home page, and they can rejoin the room again. The backend will automatically close the room after 10 minutes of inactivity (i.e., no connected clients).
TODO: We should have a new home page for users to see their active/inactive rooms (so that they can rejoin the room, or view their past collaboration sessions)
Users viewing a read-only display of a closed room
Error page template (e.g., users accessing an invalid room)
TODO: Will extend to other errors in the next PR together with BE authentication such as:
Type of change
Checklist:
pnpm lintandpnpm format