fix: Release blocker: toast with whitespace

[albinAppsmith]

Description

There was an extra space infront of toast content which cause cypress failures. This PR address that issue.

PR cause this issue: #36126

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags="@tag.All"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11121364189
Commit: a114bff
Cypress dashboard.
Tags: @tag.All
Spec:

---

Tue, 01 Oct 2024 09:28:44 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Chores
  • Minor formatting adjustments made to the Toast component.
  • Added a TODO comment regarding future accessibility features for toasts.

[coderabbitai]

Walkthrough

The changes in the Toast.tsx file involve minor formatting updates and the addition of a TODO comment focused on enhancing accessibility features for toasts. The core functionality of the Toast component and the toast object remains unchanged, ensuring that their props and behavior continue to operate as before.

Changes

File Path	Change Summary
app/client/packages/design-system/ads/src/Toast/Toast.tsx	Minor formatting adjustments, including the removal of an unnecessary space and the addition of a TODO comment regarding accessibility. No changes to functionality.

Possibly related PRs

• feat: allow multiple lines in alert component #36126: This PR modifies the Toast.tsx file by introducing a new styled component StyledPre, which is referenced in the main PR's changes to the Toast component's rendering logic.

Suggested labels

Bug, Critical, Production, Release Blocker, ok-to-test

Suggested reviewers

• hetunandu
• ApekshaBhosale

In the world of toast, a small tweak was made,
A space removed, a comment laid.
Accessibility's call, a TODO to heed,
The toast still pops, fulfilling its need.
With every click, it brings delight,
A simple change, but oh, what a sight! 🍞✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between bb11bf5 and a114bff.

📒 Files selected for processing (1)

• app/client/packages/design-system/ads/src/Toast/Toast.tsx (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• app/client/packages/design-system/ads/src/Toast/Toast.tsx

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.