Loading
Add remaining offline transfer routes, guarding with FF
What does this MR do and why?
One of two MRs that will close #586917 (closed).
- Adds routes:
- offline/import
- offline/export
- offline/import/history
- offline/export/history
- Separate controllers for offline import and offline export
- Adds basic Vue app for the export and import landing pages
What is not covered
Though the history route is added, does not create the history app as design still pending. I've created a seperate issue for later. #595227
Also, does not implement the tabbing component in the export and import pages. That will be next in the second MR (task 2) under the parent issue
See figma for Import design and Export design.
References
Screenshots or screen recordings
| Before | After |
|---|---|
![]() |
|
![]() |
How to set up and validate locally
- Navigate to /import/offline and the /export and /import subroutes. Should see a 404
- Enable THREE feature flags in rails console
offline_transfer_exports , offline_transfer_importsandoffline_transfer_ui . - Navigate to:
- /import/offline
- /import/offline/import
- /import/offline/export
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.
Related to #594811 (closed)
Edited by Oiza Baiye

