Remove multi-scenario scaffolding #24

Closed
opened 2026-03-29 23:37:35 +02:00 by myrmidex · 0 comments
Owner

Per decision in #22: one scenario per account. Remove all multi-scenario code that will never be used.

To remove:

  • Commented-out scenario CRUD routes in routes/web.php (index, create, store, edit, destroy)
  • ScenarioController methods: index(), create(), store(), edit(), destroy() — keep only show() and update()
  • Scenarios/Index.tsx frontend page
  • DeleteScenarioAction
  • StoreScenarioRequest form request
  • ScenarioRepository::getAll() method (if unused after cleanup)
  • Comments referencing "single-scenario MVP" or "re-enable later" — this is now permanent architecture

To update:

  • routes/web.php comment: change "Single-scenario MVP" to permanent routing
  • Remove "re-enable later" comments from routes and auth dashboard

Keep:

  • CreateScenarioAction (used by seeder for initial scenario)
  • UpdateScenarioAction + UpdateScenarioRequest (settings panel)
  • ScenarioController::show() and update()
  • Scenario model and migration (still needed, just one per user)
Per decision in #22: one scenario per account. Remove all multi-scenario code that will never be used. **To remove:** - Commented-out scenario CRUD routes in `routes/web.php` (index, create, store, edit, destroy) - `ScenarioController` methods: `index()`, `create()`, `store()`, `edit()`, `destroy()` — keep only `show()` and `update()` - `Scenarios/Index.tsx` frontend page - `DeleteScenarioAction` - `StoreScenarioRequest` form request - `ScenarioRepository::getAll()` method (if unused after cleanup) - Comments referencing "single-scenario MVP" or "re-enable later" — this is now permanent architecture **To update:** - `routes/web.php` comment: change "Single-scenario MVP" to permanent routing - Remove "re-enable later" comments from routes and auth dashboard **Keep:** - `CreateScenarioAction` (used by seeder for initial scenario) - `UpdateScenarioAction` + `UpdateScenarioRequest` (settings panel) - `ScenarioController::show()` and `update()` - Scenario model and migration (still needed, just one per user)
myrmidex added this to the v0.2.0 milestone 2026-03-29 23:37:35 +02:00
myrmidex added the
enhancement
label 2026-03-29 23:37:35 +02:00
myrmidex self-assigned this 2026-03-29 23:37:35 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lvl0/buckets#24
No description provided.