Ensure that the API for export_requests in the AdminService are consistent and properly documented.
Currently the API diverges from the documentation, and the exportFormats contains both the format (csv/graphml), and the csv specific options (because the csv can export additional files).
Deliverables:
Update endpoint to separate format and options
Update related documentation
An upcoming change is to allow graphml to include ego data, so this needs to be factored in to the new design. My inclination would be to change csvOptions to a generic options property and check for compatibility / ignore superfluous options when handling the request.
Ensure that the API for export_requests in the AdminService are consistent and properly documented.
Currently the API diverges from the documentation, and the exportFormats contains both the format (csv/graphml), and the csv specific options (because the csv can export additional files).
Deliverables:
csvOptionsto a genericoptionsproperty and check for compatibility / ignore superfluous options when handling the request.For current implementation see /src/main/server/AdminService.js and /src/main/data-managers/ExportManager.js
May relate to: https://github.com/codaco/network-exporters/issues/1