migrate archive code into repo layer #352
Labels
development
Issues that require technical work. Associated PRs are required.
enhancement
Issues & PRs that capture enhancements to existing features. Issues require associated PRs.
Is your enhancement request related to a problem? Please describe
the new archiving functionality leverages a lot of repo layer functionality in the client
Describe the solution you'd like
the majority of the archiving code, specifically anything leveraging the repo directly, should be moved into the repo layer on the
BaseRepository
objectAdditional context
the remaining client code should probably look something like this. it may be necessary to leave other things in or generate inputs at the client level that I'm not noticing at the moment
The text was updated successfully, but these errors were encountered: