RocketChat / RocketChat/Rocket.Chat

Duplicate Toast Notification on "Invite Link" Action

Open
#35,335 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

When a user attempts to invite another user to a public or private channel in the Rocket.Chat web application by clicking the "Invite Link" button, the system generates the invite link correctly. However, it displays the "Invite link has been generated" message twice, showing two identical toast notifications simultaneously.

Steps to reproduce:
  1. Navigate to any public or private channel.
  2. Click on the "Invite" button to add a new user.
  3. Select the "Invite Link" option.
  4. Observe that two identical toast notifications appear instead of one.
Expected behavior:

Only a single toast notification should be displayed when the invite link is generated.

Additional context

Rocket.Chat uses Fuselage Toast for notifications. The issue might be related to redundant triggers for the toast component in the codebase.

While this might seem like a small issue, it could be a good first issue for new contributors or may need attention to improve the user experience.

https://github.com/user-attachments/assets/d5c8f935-3dc6-492d-8459-df01b3e40447

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Invite Link action in the Rocket.Chat web application and the Fuselage Toast notification triggers involved in generating the link. Reproduce the issue using the listed steps, identify why the message appears twice, and verify that generating an invite link displays only one toast.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.