fix(ui): remove route-triggered effect auto-apply

[hyperb1iss]

Motivation

• Prevent a navigable SPA GET route (/effects/:id) from causing an implicit first-party POST mutation (/api/v1/effects/{id}/apply) by removing client-side logic that auto-applied effects when that route parameter was present.

Description

• Remove use_params_map usage and the route-parameter wiring from crates/hypercolor-ui/src/pages/effects.rs and delete the reactive Effect that automatically called fx.apply_effect(...) on route navigation so effect application requires an explicit in-app action.

Testing

• Ran cargo check --workspace in this environment but the full compilation did not complete within the interactive session, so no final pass/fail was captured.

---

Codex Task

Summary by CodeRabbit

• Refactor
  • Removed URL parameter-based effect routing logic from the Effects page, simplifying the effect application flow.

[coderabbitai]

Warning

Rate limit exceeded

@hyperb1iss has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 49 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: af5dd028-6508-4fcc-8e42-b5e8b2d290b1

📥 Commits

Reviewing files that changed from the base of the PR and between aaaa47b and ee3df16.

📒 Files selected for processing (1)

• crates/hypercolor-ui/src/pages/effects.rs

📝 Walkthrough

Walkthrough

EffectsPage removes 29 lines of URL-parameter-based routing logic. The use_params_map() hook, the routed_effect_id memo, and the effect synchronization block that watched route changes are deleted, eliminating URL-to-effect-ID binding.

Changes

Cohort / File(s)	Summary
Route parameter removal from EffectsPage crates/hypercolor-ui/src/pages/effects.rs	Removed URL parameter handling and effect-ID synchronization: deleted use_params_map import, removed routed_effect_id memo derivation, and eliminated Effect::new block that applied effects on route changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

---

🐰 Route params fade away, no more IDs in URL play,
Effects now dance to a different way,
The router's grip is loosened today,
Simpler paths for the UI to sway!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 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: removing route-triggered automatic effect application logic from the effects page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/propose-fix-for-vulnerability-in-effects-route

---

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.}