Omnichannel → Livechat Triggers: Whitespace-only values accepted in Name, Description and Message fields

[Codersintu]

Description:

While testing the Omnichannel → Livechat Triggers creation form, I noticed that the required text fields accept whitespace-only values.
Currently, entering only spaces (" ") in Name, Description, or Message enables the Save button and allows the trigger to be created successfully.

This results in invalid/empty-looking triggers being stored.

Steps to reproduce:

1. Go to Settings → Omnichannel → Livechat Triggers
2. Click Create trigger
3. Enter spaces only (" ") in:
   i) Name
   ii) Description
   iii) Message
4. Click Save

Expected behavior:

 1. Fields should be trimmed before validation
 2.  Whitespace-only values should be treated as empty

Actual behavior:

Trigger is created successfully with whitespace-only values

Server Setup Information:

• Version of Rocket.Chat Server: develop branch (local build)
• License Type: Community
• Number of Users: 1
• Operating System: Linux (GitHub Codespaces)
• Deployment Method: yarn dsv
• Number of Running Instances: 1
• DB Replicaset Oplog: disabled
• NodeJS Version: v22.16.0

Client Setup Information

• Desktop App or Browser Version: Chrome
• Operating System: Windows/Linux

Additional context

This appears to be a frontend validation issue. Inputs are not trimmed before validation, allowing whitespace-only values to pass required checks.

whitespace.error.1.mp4

[Codersintu]

Hi, I’d like to work on this issue.
I have started investigating and preparing a fix for the whitespace validation problem.
I will submit a PR shortly.

[dhruvjamwal]

Hello @Codersintu,
I have try fixed this issue by adding .trim().

1. Fields should be trimmed before validation
2. Whitespace-only values should be treated as empty
   Please suggest any further changes. required..

[KevLehman]

This pull request has been inactive for a while, so we’re closing it to keep the backlog manageable.
If you’d like to continue working on it, feel free to reopen or submit a new PR. Thanks for the contribution!

[Codersintu]

Hey @KevLehman , since the previous PR was closed, I’d like to work on this issue and submit a fresh fix. I’ll open a PR shortly