feat: add Database AI suggestions bottom alert

[HarshMN2345]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• New Features
  • Database AI suggestions promotion now available for cloud users, highlighting the ability to generate database schemas directly from table names with a single click.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Environment variables can be scoped per function or shared across your project

[coderabbitai]

Walkthrough

The pull request modifies src/routes/(console)/bottomAlerts.ts to replace a database operators promotional notification with an AI suggestions promotional notification in cloud environments. The change involves updating imports to reference AI suggestions images instead, renaming the promo object, updating the modal ID, and revising the promotional title, message, and call-to-action link to reflect the new feature announcement.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Single file modified with consistent pattern of promo property swaps
• Straightforward string replacements and import updates
• No changes to control flow or logic structure
• Low risk of unintended side effects

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding a Database AI suggestions bottom alert, which aligns with the file modifications replacing DB Operators promo with AI suggestions promo.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat-SER-645-Console-Notification-Database-AI-suggestions

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b175e08 and 7d24475.

⛔ Files ignored due to path filters (4)

• src/lib/images/promos/ai-suggestions-dark.png is excluded by !**/*.png
• src/lib/images/promos/ai-suggestions-light.png is excluded by !**/*.png
• src/lib/images/promos/db-operators-dark.png is excluded by !**/*.png
• src/lib/images/promos/db-operators-light.png is excluded by !**/*.png

📒 Files selected for processing (1)

• src/routes/(console)/bottomAlerts.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (4)

**/*.{ts,tsx,js,jsx,svelte}

📄 CodeRabbit inference engine (AGENTS.md)

**/*.{ts,tsx,js,jsx,svelte}: Import reusable modules from the src/lib directory using the $lib alias
Use minimal comments in code; reserve comments for TODOs or complex logic explanations
Use $lib, $routes, and $themes aliases instead of relative paths for module imports

Files:

• src/routes/(console)/bottomAlerts.ts

**/*.ts

📄 CodeRabbit inference engine (AGENTS.md)

**/*.ts: Define types inline or in .d.ts files, avoid creating separate .types.ts files
Use TypeScript in non-strict mode; any type is tolerated in this project

Files:

• src/routes/(console)/bottomAlerts.ts

**/*.{ts,tsx,js,jsx,svelte,json}

📄 CodeRabbit inference engine (AGENTS.md)

Use 4 spaces for indentation, single quotes, 100 character line width, and no trailing commas per Prettier configuration

Files:

• src/routes/(console)/bottomAlerts.ts

src/routes/**

📄 CodeRabbit inference engine (AGENTS.md)

Configure dynamic routes using SvelteKit convention with [param] syntax in route directory names

Files:

• src/routes/(console)/bottomAlerts.ts

🧠 Learnings (1)

📓 Common learnings

Learnt from: atharvadeosthale
Repo: appwrite/console PR: 2512
File: src/routes/(console)/project-[region]-[project]/overview/platforms/llmBanner.svelte:51-83
Timestamp: 2025-11-19T11:22:42.553Z
Learning: In src/routes/(console)/project-[region]-[project]/overview/platforms/llmBanner.svelte, the Lovable integration URL format `https://lovable.dev/` with `autosubmit` and `prompt` as query parameters (set via searchParams) is correct and functional.

🧬 Code graph analysis (1)

src/routes/(console)/bottomAlerts.ts (1)

src/lib/system.ts (1)

• isCloud (26-26)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: e2e
• GitHub Check: build

🔇 Additional comments (2)

src/routes/(console)/bottomAlerts.ts (2)

4-5: AI suggestions promo image imports are clear and follow aliases

Using $lib/images/promos/... for the dark/light assets matches the alias guidelines, and the naming is consistent and self-explanatory.

---

10-29: Cloud‑only AI suggestions promo configuration looks consistent

The new aiSuggestionsPromo object is correctly gated by isCloud, uses a distinct modal id, wires the dark/light images properly, and the CTA targets the AI suggestions blog URL. Shape and field values align with the existing BottomModalAlertItem pattern, so this should drop in without behavioral regressions.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}