[WIP] feat(migration): Improve mail import/export functionality #12382
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work in progress!
Overview
This pull request extends the previous MVP import/export functionality. The following things are now being migrated as well:
Open tasks
@return arraydescription regarding the mappingOpen questions by myself
I was confused about the architecture. There are the
mapperclasses, which sometimes are being used viaservices. But sometimes they are used directly (examples:MailboxMapper,ActionStepMapper,TagMapper). When is it advised to create a service class instead of using the mapper directly? 🤔Relates to #12001.