chore: add messages for chrome extension banner

[jsartisan]

Summary by CodeRabbit

• New Features
  • Enhanced in-app messaging now highlights the Chrome extension. Users will see a new banner featuring a title, a brief description, and a button that showcases the benefits of integrating powerful AI assistance into your daily tools.

Warning

Tests have not run on the HEAD adbada2 yet

---

Wed, 09 Apr 2025 05:22:23 UTC

[coderabbitai]

Walkthrough

This PR introduces three new properties to the IN_APP_EMBED_SETTING object in the app/client/src/ce/constants/messages.ts file. These properties, chromeExtensionBannerTitle, chromeExtensionBannerDescription, and chromeExtensionBannerButton, are functions that return specific strings related to the Chrome extension. The changes enhance the messaging within the application settings to inform users about the Chrome extension's availability and benefits.

Changes

File	Change Summary
app/client/src/ce/constants/messages.ts	Added chromeExtensionBannerTitle returning "Get the Chrome extension", chromeExtensionBannerDescription returning "Bring powerful AI assistance to the tools you and your teams use.", and chromeExtensionBannerButton returning "Get the extension".

Possibly related PRs

• chore: Add chrome extension link in embed #40179: Introduces the ChromeExtensionBanner component, aligning with the messaging changes for the Chrome extension.

Suggested reviewers

• ankitakinger
• hetunandu

Poem

In our code, a new message takes flight,
Words now guide users with a touch so light.
A banner of extension, bold and clear,
Invites a future where assistance is near.
Code blossoms with this delightful display,
A small change that brightens up the day.
🚀 Happy coding!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between bd25c7f and adbada2.

📒 Files selected for processing (1)

• app/client/src/ce/constants/messages.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: client-unit-tests / client-unit-tests
• GitHub Check: client-lint / client-lint
• GitHub Check: client-build / client-build
• GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
• GitHub Check: client-prettier / prettier-check

🔇 Additional comments (1)

app/client/src/ce/constants/messages.ts (1)

1999-2002: The Chrome extension banner messages have been added correctly.

These new message constants follow the established pattern in the file, using arrow functions that return string literals. The property names are descriptive and use proper camelCase convention.

---

🪧 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 plan to trigger planning for file edits and PR creation.
• @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.