Write Unittests for src/screens/UserPortal/Chat/Chat.tsx

[palisadoes]

We will need unittests done for all methods, classes and functions found in this file.

PR Acceptance Criteria

1. When complete this file must show 100% coverage when merged into the code base.
2. The current code coverage for the file can be found here
3. CodeRabbit must approve all your changes to the test file(s) and the file(s) under test
4. The PR will show a report for the code coverage for the file you have added. You can use that as a guide
5. No functionality must be removed to achieve this goal
6. All tests must be valid and truly test the code base

Other Criteria

1. If this file isn't referenced in the code base then remove it. We don't want tests run on unused code

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[rachit124]

I would like to work on this issue.
Looking forward to your guidance.
Best regards,
Rachit Prakash

[rachit124]

Hello sir, I'm having some issues running the program. Could you please help me resolve this issue?

[palisadoes]

Here is Our Getting Started - Developers YouTube playlist, it has all you need to know to get started. Please listen to all of them as they will help to set your expectations.
https://www.youtube.com/watch?v=YpBUoHxEeyg&list=PLv50qHwThlJUIzscg9a80a9-HmAlmUdCF&pp=gAQBiAQB

[Kunalpal216]

If there are no updates by @rachit124 , Can this issue be assigned to me ?

[rachit124]

hi I'm trying please can you pick some other issue

[palisadoes]

During the week of November 11, 2024 we will start a code freeze on the develop branches in Talawa, Talawa Admin and Talawa-API.

We have completed a project to convert the Talawa-API backend to use PostgreSQL. Work will then begin with us merging code in the develop branches to a new develop-postrgres branch in each repository.

Planning activities for this will be managed in our #talawa-projects slack channel. A GitHub project will be created to track specially labeled issues. We completed a similar exercise last year using a similar methodology.

Starting November 12, California time no new PRs will be accepted against the develop branch. They must be applied to the develop-postrgres branch.

There are some GSoC project features that will need to be merged into develop. These will be the only exceptions.

This activity and the post GSoC 2024 start date was announced in our #general Slack channel last month as a pinned post.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

@rachit124 Are you still working on this?

[aditya-bansal-7]

if there are no updates I can work on this issue?

[rachit124]

I need some time
I apologise for taking so much time.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

@rachit124

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

[JYOTI-SHREE28]

can you please assign this issue to me

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue.

[NishantSinghhhhh]

@palisadoes, @Cioppolo14 think this issue is already completed

#3163