Repository navigation
feat(web): Maple's alerts go through its bot - #373
Conversation
Maple now posts alerts through the same bot that answers in threads, and retired its separate alert webhook integration. The Maple integration page's alerts panel says so and links to Maple's alert routing, where a Hazel channel is picked once the bot is installed, instead of the retired ?integration=hazel entry.
Maple review🟢 Confidence 10/10 · safe to merge. Contained view/copy change; all four call sites of the reshaped helpers are updated and the scene test asserts both new alert links. Splits the Maple alerts links off
|
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Define Maple URLs apps/web-foldkit/src/page/settings/integrations/detail/view-maple.ts |
mapleIntegrationUrl now always builds the chat-hazel integration URL. mapleAlertsUrl builds a separate alerts-routing URL, and euLink accepts a complete destination URL. |
Wire Maple page links apps/web-foldkit/src/page/settings/integrations/detail/view-maple.ts, apps/web-foldkit/src/page/settings/integrations/detail/scene.test.ts |
Management and connection links use the integration URL. Alert setup links use the alerts-routing URL. The page descriptions and tests reflect the bot and routing changes. |
Estimated code review effort: 2 (Simple) | ~10 minutes
Possibly related PRs
- MapleTechLabs/hazel#371: Adds the Maple integration page and bot-install flow updated here.
- MapleTechLabs/hazel#370: Provides the bot-install contract and consent flow used by Maple’s connection path.
Merge Risk: 
e24b1
-
The Maple integration and alert links are consistent with the stated routing flow, with no confirmed merge-blocking risk.
Pre-merge checks: 
-
Check name Status Explanation Description Check Check skipped - CodeRabbit’s high-level summary is enabled. Title check The title clearly and concisely describes the main change: Maple alerts now use its bot. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 2 files.
-
Finishing Touches
-
Generate docstrings
-
- Commit to this branch
- Create a new PR
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
Follow-up to #371. Maple is merging its two Hazel integrations into one bot (MapleTechLabs/maple#2022): the bot that answers
@Maplein threads now also posts alerts, and the separate alert webhook integration is gone.The Maple integration page's Alerts panel now says alerts go through the same bot. Set up alerts in Maple (US and EU) links to Maple's alert routing (
/alerts?tab=routing), where a Hazel channel is picked as a destination, instead of?integration=hazel. Maple redirects that old link to the bot's page anyway, so nothing breaks before this deploys.Verification
settings/integrations/detail.tscclean inapps/web-foldkit, oxlint clean.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by CodeRabbit