Clean up legacy JSON fixtures and tree_saver for Import/Export
requested to merge 396655-clean-up-legacy-json-fixtures-and-tree_saver-for-import-export into master
What does this MR do and why?
This MR removes deprecated fixtures for the legacy JSON reader
- spec/fixtures/lib/gitlab/import_export/complex/project.json
- spec/fixtures/lib/gitlab/import_export/designs/project.json
- spec/fixtures/lib/gitlab/import_export/group/project.json
- spec/fixtures/lib/gitlab/import_export/group_exports/complex/group.json
- spec/fixtures/lib/gitlab/import_export/group_exports/no_children/group.json
- spec/fixtures/lib/gitlab/import_export/group_exports/visibility_levels/internal/group.json
- spec/fixtures/lib/gitlab/import_export/group_exports/visibility_levels/private/group.json
- spec/fixtures/lib/gitlab/import_export/group_exports/visibility_levels/public/group.json
- spec/fixtures/lib/gitlab/import_export/invalid_json/project.json spec/fixtures/lib/gitlab/import_export/light/project.json
- spec/fixtures/lib/gitlab/import_export/milestone-iid/project.json
- spec/fixtures/lib/gitlab/import_export/multi_pipeline_ref_one_external_pr/project.json
- spec/fixtures/lib/gitlab/import_export/with_invalid_records/project.json
- ee/spec/fixtures/lib/gitlab/import_export/complex/project.json
- ee/spec/fixtures/lib/gitlab/import_export/group_exports/light/group.json
In addition, it also removes lib/gitlab/import_export/legacy_relation_tree_saver.rb
that we forgot to delete in !105087 (merged)
Screenshots or screen recordings
N/A
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #396655 (closed)
Edited by Martin Wortschack