Skip to content

Remove broken Saved Scenario Reports feature#4750

Open
aaccensi wants to merge 1 commit into
masterfrom
cleanup-saved-scenario-reports
Open

Remove broken Saved Scenario Reports feature#4750
aaccensi wants to merge 1 commit into
masterfrom
cleanup-saved-scenario-reports

Conversation

@aaccensi

@aaccensi aaccensi commented Jul 14, 2026

Copy link
Copy Markdown
Member

Context

While removing the Energy Mix infographic and adding the deprecation notice to the Scenario Report feature, some queries turned up that belonged to a different, forgotten feature: a CSV export for saved scenarios (/saved_scenarios/:id/report/:report_name) driven by a YAML query template. It dates from when saved scenarios still lived in etmodel and has been broken since they moved to MyETM. It has been broken for a long time with no complaints, so this PR removes it entirely rather than fixing it.

Implemented changes

  • Removed SavedScenarioReportsController (broken CSV report controller)
  • Removed the CSV view template app/views/saved_scenario_reports/show.csv.erb
  • Removed the FetchAPIScenarioQueries service and its spec (only used by this controller)
  • Removed config/saved_scenario_reports/ovm.yml, the only report config (directory deleted too)
  • Removed the route get '/report/:report_name' => 'saved_scenario_reports#show' from config/routes.rb
  • Removed the Engine::Query model — orphaned once the service was deleted (its sole consumer)

Related

Closes #4669

Checklist

  • I have tested these changes
  • I have updated documentation as needed
  • I have tagged the relevant people for review

Deletes the CSV report controller, view, FetchAPIScenarioQueries
service, ovm.yml report config, route, and the now-orphaned
Engine::Query model. Broken since saved scenarios moved to MyETM.

Fixes #4669
@aaccensi
aaccensi requested a review from noracato July 14, 2026 15:47

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was just orphaned anyways right?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, this was just old orphaned files and a route

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cleanup of old/broken Saved Scenario Reports feature

2 participants