This code updates the backend API and addresses previous PR requests Comments and suggestions before accidental merge.
## [24](https://github.com/mustafa-tariqk/mindscape/issues/24)
Resolves: Chat Room Features #24
The updated features for the basic implementation of the frontend chatpage
## Author checklist
If any of these points have yet to be satisfied, make sure that you set the title to the format DRAFT #issue-num Title
- [x] The title is short and descriptive of the PR. Must start with the Github Issue Number (format: #issue-num Title).
- [x] The description follows proper cl description practices and mentions related Github Issues (make sure this is the first thing you mention).
- [x] Branch has merged in the **latest version of main**
- [ ] **Linting** has occured, as per the project linting config
- [x] All changed functions have proper **docstring/wiki updates (front-end team)** to describe what they do and how to use them.
- [x] Add yourself as the assignee.
- [x] Add reviewer a reviewer and let them know on discord.
- [x] Ensure that all relevant ticket has been linked to the PR
## Reviewer checklist
- [ ] Relevant issue is mentioned in description
- [ ] Code solves the issue
- [ ] Code follows the specification
- [ ] Code is the best solution for the issue
- [ ] Branch is **ahead of main**
- [ ] Ensures the fix/feature works locally
What does this PR do?
This code updates the backend API and addresses previous PR requests Comments and suggestions before accidental merge. ## [24](https://github.com/mustafa-tariqk/mindscape/issues/24)Resolves: Chat Room Features #24
The updated features for the basic implementation of the frontend chatpage ## Author checklist If any of these points have yet to be satisfied, make sure that you set the title to the format DRAFT #issue-num Title - [x] The title is short and descriptive of the PR. Must start with the Github Issue Number (format: #issue-num Title). - [x] The description follows proper cl description practices and mentions related Github Issues (make sure this is the first thing you mention). - [x] Branch has merged in the **latest version of main** - [ ] **Linting** has occured, as per the project linting config - [x] All changed functions have proper **docstring/wiki updates (front-end team)** to describe what they do and how to use them. - [x] Add yourself as the assignee. - [x] Add reviewer a reviewer and let them know on discord. - [x] Ensure that all relevant ticket has been linked to the PR ## Reviewer checklist - [ ] Relevant issue is mentioned in description - [ ] Code solves the issue - [ ] Code follows the specification - [ ] Code is the best solution for the issue - [ ] Branch is **ahead of main** - [ ] Ensures the fix/feature works locally