Currently, get email flow and search email flow are using the same api/data source/repository methods.
To better separate the concern of each flow, and implement Search snippet, search email flow will now using different api/data source/repository methods.
The search email api method now combine Email/query, SearchSnippet/get and Email/get, which returns SearchEmailsResponse, extending EmailsResponse, with additional property SearchSnippet.
ThreadRepositoryImpl's searchEmails method, instead of using getAllEmail from data source, now use search email method and returning List<SearchEmail>, in which SearchEmail extends from Email with 2 additional properties String? searchSubject and String? searchPreview.
DoDs
[ ] Implement API, data source & repository layers
[ ] Write unit tests
[ ] Create SearchPresentationEmail extend PresentationEmail, with 2 additional properties String? searchSubject and String? searchPreview.
[ ] Write an extension of SearchEmail called toSearchPresentationEmail which transform SearchEmail to SearchPresentationEmail, and unit test this method
Description
get emailflow andsearch emailflow are using the same api/data source/repository methods.search emailflow will now using different api/data source/repository methods.search emailapi method now combineEmail/query,SearchSnippet/getandEmail/get, which returnsSearchEmailsResponse, extendingEmailsResponse, with additional propertySearchSnippet.ThreadRepositoryImpl'ssearchEmailsmethod, instead of usinggetAllEmailfrom data source, now usesearch emailmethod and returningList<SearchEmail>, in whichSearchEmailextends fromEmailwith 2 additional propertiesString? searchSubjectandString? searchPreview.DoDs
SearchPresentationEmailextendPresentationEmail, with 2 additional propertiesString? searchSubjectandString? searchPreview.SearchEmailcalledtoSearchPresentationEmailwhich transformSearchEmailtoSearchPresentationEmail, and unit test this method