Data Management - Update FE to support plural routes
What does this MR do and why?
This change is behind the feature flag Feature.enable(:geo_primary_verification_view)
This change updates the frontend to key off the plural version of each model to match the updated route and API expectations implemented in !214542 (merged)
important: The routing is in progress of moving to plural routes: #582209
Screenshots or screen recordings
| Before | After | |
|---|---|---|
| List View |
|
|
| Details View |
|
|
How to set up and validate locally
Setup Geo (optional)
Important: To properly test Geo you will need a separate GDK setup. Setup is straightforward but takes some time. Another option is to validate the code functionally and if needed schedule a call to sync and I can screen share my instance.
- Ensure no other GDKs are running.
gdk stop/gdk kill - Open an empty directory and install and run Geo with the one-line command found on the Easy installation instructions
- Access your primary and secondary Geo instances via
127.0.0.1:3000and127.0.0.1:3001.
Testing
- Enable Feature Flag (
Feature.enable(:geo_primary_verification_view)) - Navigate to
/admin/data_management/uploads - Ensure route does not 404
- Click into one of the records
- Ensure route is
/admin/data_management/uploads/${ID}and does not 404
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Zack Cuddy



