Please do not post any internal, closed source snippets on this public issue tracker!
Purpose
_Please describe the end goal you are trying to achieve that has led you to request this feature._
The implementations of import and export vary quite widely depending on the source/target formats, and are currently held together with duct tape. With the benefit of hindsight of numerous supported formats, the problem is relatively simple, so the inconsistencies in these APIs should be addressed.
Suggested approaches
What have you tried, and how might this problem be solved?
Both import and export should support single and multiple files (e.g. SQL migrations scripts are a multi-file representation of a single model).
Both import and export CLI APIs should have similar behaviours (e.g. output to stdout by default).
In particular, arr.ai should be supported as the primary driver of both importing and exporting.
Acceptance Criteria
Approved design doc describing:
CLI API
Internal interfaces for importers and exporters
Conventions for describing how to input/output multiple files
Please do not post any internal, closed source snippets on this public issue tracker!
Purpose
_Please describe the end goal you are trying to achieve that has led you to request this feature._
The implementations of import and export vary quite widely depending on the source/target formats, and are currently held together with duct tape. With the benefit of hindsight of numerous supported formats, the problem is relatively simple, so the inconsistencies in these APIs should be addressed.
Suggested approaches
What have you tried, and how might this problem be solved?
Acceptance Criteria
Approved design doc describing: