Resonate icon indicating copy to clipboard operation
Resonate copied to clipboard

No Option to Delete Created Rooms

Open Sharma-Ji-21 opened this issue 8 months ago β€’ 1 comments

πŸš€ The feature

Description:

Currently, after creating a room, there is no option to delete it from the UI. Users should have the ability to remove rooms they no longer need.

Expected Behavior: β€’ A delete button should be added to each room card, allowing users to remove unwanted rooms. β€’ The app should ask for confirmation before deleting a room to prevent accidental deletions. β€’ Once deleted, the room should disappear from the list immediately.

Steps to Reproduce: 1. Create a new room. 2. Go back to the homepage. 3. Notice that there is no option to delete the room.

Motivation, pitch

Motivation: The ability to delete rooms is essential for maintaining a clean and manageable user experience. Without a delete option, users are forced to keep unwanted rooms, leading to clutter and potential frustration. This issue becomes even more significant as more rooms are created, making it harder to navigate and organize active discussions.

Pitch: Implementing a delete button will enhance user control over their created rooms, allowing them to remove unnecessary or outdated rooms. This feature will improve the app’s usability, making it more intuitive and efficient. Adding a confirmation prompt before deletion ensures that rooms are not removed accidentally, balancing functionality with user safety.

Sharma-Ji-21 avatar Mar 26 '25 11:03 Sharma-Ji-21

@Aarush-Acharya @chandansgowda please assign this to me

Sharma-Ji-21 avatar Mar 26 '25 11:03 Sharma-Ji-21

Hi! πŸ‘‹ I'd love to work on this issue. I have worked with a similar issue of deleting a Proposed Fix: Add a delete icon (e.g., trash bin) next to rooms the current user has created (in the room list or room details). It can also be modified that the user / room creator gets a list of rooms that he wants to delete

the image below is form my project i have worked in... Image

On tap, the user with a confirmation dialog (e.g., β€œAre you sure you want to delete this room?”).

If confirmed: Remove the room entry from the database, refresh the room list to reflect the deletion. Ensure only the room creator (or users with appropriate permissions) sees the delete option.

If this approach sounds good, I'd be happy to go ahead and open a PR!

sandy4242 avatar Jul 20 '25 04:07 sandy4242

Hey @sandy4242 , as @Sharma-Ji-21 requested to work on the issue first, will assign to him. Thank you for your interest!

@Sharma-Ji-21 you can start working on this

M4dhav avatar Jul 31 '25 23:07 M4dhav

@M4dhav hey how I get inti contributing here, most of issues are given by the contributors themselves...so no scope for new comers to contribute here!!

sandy4242 avatar Aug 01 '25 06:08 sandy4242

Hey @sandy4242 , you can take a look at #497 and #498 or you can run the app locally and think about some feature you would like to add which would be valuable to the community, or fix any bugs that you end up finding.

M4dhav avatar Aug 01 '25 13:08 M4dhav

@sandy4242 as there has been no activity on this issue for a month, you can take this up if you want, please confirm and I will reassign the issue

M4dhav avatar Aug 28 '25 12:08 M4dhav

i would like to work on this

Mayank4352 avatar Aug 31 '25 15:08 Mayank4352

Assigning to you @Mayank4352

M4dhav avatar Aug 31 '25 16:08 M4dhav

umm was i late to take up this issue @M4dhav?

sandy4242 avatar Sep 01 '25 17:09 sandy4242

Hey @sandy4242 , since there was no response from your side I did not assign it to you, I am sorry about that.

M4dhav avatar Sep 01 '25 18:09 M4dhav

not an issue @M4dhav, well if again faced with same issue of inactivity, do assign it to me, happy to help.

sandy4242 avatar Sep 01 '25 18:09 sandy4242

or any open issues that you would recommend me to work / look into? @M4dhav

sandy4242 avatar Sep 01 '25 18:09 sandy4242

@sandy4242 there are a couple of issues you can take a look at, #465 #460 #442 #415 #519

M4dhav avatar Sep 01 '25 18:09 M4dhav

Hey @Mayank4352 , any updates on this?

M4dhav avatar Sep 19 '25 10:09 M4dhav

I'm working on this, will be done by next week

Mayank4352 avatar Sep 19 '25 11:09 Mayank4352

will u please assign this issue to me @M4dhav i will get done with it easily

The room disappears immediately after deletion.

A SnackBar or toast confirms successful removal.

Errors gracefully notify the user.

4555jan avatar Sep 27 '25 04:09 4555jan

Hey @4555jan I've already completed this, waiting for him to review my existing pr, then I'll open pr for this

Mayank4352 avatar Sep 27 '25 04:09 Mayank4352

@Mayank4352 you already opned the pull request ? can we please talk on discord ? i have a doubt regrading something

4555jan avatar Sep 27 '25 04:09 4555jan

At work currently

Mayank4352 avatar Sep 27 '25 04:09 Mayank4352

Closing as fixed by #557 and #590

M4dhav avatar Nov 11 '25 19:11 M4dhav

πŸ”’ Issue Closed - Thank You, @M4dhav!
This issue has been resolved or is no longer relevant.

  • If you have further questions, feel free to open a new issue. πŸ’‘

Thanks for helping improve the project! πŸš€

github-actions[bot] avatar Nov 11 '25 19:11 github-actions[bot]

Hey @Mayank4352 sorry, I forgot to ask you to add tests within the PR, could you please add tests for this functionality

M4dhav avatar Nov 12 '25 13:11 M4dhav

Hey @M4dhav, As i mentioned in #556 adding unit tests to upcoming_room_controller is not possible currently without extensive refactoring due to it being too tightly coupled with room_controller. I'd like to hear your thoughts regarding the same

Mayank4352 avatar Nov 12 '25 16:11 Mayank4352

Then leave the tests for the coupled functions but write the tests for the functions you implemented. If even they are coupled, then decouple them and write tests for them

M4dhav avatar Nov 13 '25 07:11 M4dhav

I had to refactor the upcoming_room controller, it was untestable as there were many hard coded intialized controllers(direct Get.find()) that were making it untestable. I refactored the UpcomingRoomController to remove the direct Get.find() calls from field initializers, which made the controller untestable since those initializers run before the constructor. The controller now uses constructor-based dependency injection, following the same testable pattern used in ChangeEmailController and EditProfileController. This makes the logic easier to mock and ensures the controller is testable

Mayank4352 avatar Nov 13 '25 10:11 Mayank4352

Closing as tests are added in #595

M4dhav avatar Nov 14 '25 07:11 M4dhav

πŸ”’ Issue Closed - Thank You, @M4dhav!
This issue has been resolved or is no longer relevant.

  • If you have further questions, feel free to open a new issue. πŸ’‘

Thanks for helping improve the project! πŸš€

github-actions[bot] avatar Nov 14 '25 07:11 github-actions[bot]