New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rewrite epiv2 exports #870
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! There were some commented TODOs left in here that I think should be addressed before merge, which makes up the bulk of the comments I left. Also once those are wrapped up you should regenerate the VCR fixture for the epi api test so that it passes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, you've convinced me, this is a nice pattern! Some feedback on the API and layout
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I made two minor changes, if you're ok with these. I figure in the future we'll get rid of the FlatFileExporter and just use this Export class directly; you can see I was able to do so in the epiv2 api (but couldn't get rid of it b/c the DataPivotQuery still uses the old one).
Rewrite how the epiv2 export is calculated to combine multiple django ORM queries into a single request.
No changes were made to the export format of the data itself.
This PR created two new base classes,
ModelExport
, andExporter
, that we'll use throughout the application to update our modernize our existing export formats.