Open saeliddp opened 5 months ago
Some thoughts I had recently related to further curation refactoring:
CurationImageLoader
violates the principles behind the initial refactor because it runs async code and curationModel
has a reference to it. This makes testing tricky, which is what we want to avoid. I'm wondering if it would be possible to deprecate the image loader and instead use the model/service pattern for all of our needs here.
From review w/ brian and chris:
Could store state directly in curation record list instead of storing it as fields and then saving fields when next is hit