Discussion: Rule of thumb for developers when importing an existing user #1090
Closed
DerDreschner
started this conversation in
General
Replies: 1 comment 1 reply
-
|
For me option 1 is the goal. That’s how it works with files, import the ones from the archive, do not delete existing ones (unless there is the same path in the import). |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Alright, thanks for clarification! I've created a new issue to handle a potential "cleanup" before importing in the future (#1096). |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The following question popped up during development of an enhanced user migration for the mail app.
Right now, the documentation doesn't specify how to handle existing data during import. There are two different approches to it:
Sure it depends on what is being imported. But there is no rule of thumb being documented right now and the notices during import (at least when using the CLI) can be treated as "that can happen" (1) as well as "this will happen" (2).
So, what is your point of view here?
Beta Was this translation helpful? Give feedback.
All reactions