Please check if the PR fulfills these requirements(please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)
[ X] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
Does this PR already have an issue describing the problem ?If so, link to this issue using '#XXX' and skip the rest
no
What kind of change does this PR introduce?(Bug fix, feature, docs update, ...)
feature
What is the current behavior?(You can also link to an open issue here)
When importing into a folder, if an object is named after the imported one, you can not overwrite it and get an error message.
What is the new behavior (if this is a feature change)?
When importing into a folder, if an object is named after the imported one, three options are proposed:
Overwrite the object
Rename the imported object
Cancel the import
Does this PR introduce a breaking change or deprecate an API?If yes, check the following:
[ ] The Breaking Change or Deprecated label has been added
[ ] The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)
No braking change
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)
Please check if the PR fulfills these requirements (please use
'[x]'to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'and skip the rest noWhat kind of change does this PR introduce? (Bug fix, feature, docs update, ...) feature
What is the current behavior? (You can also link to an open issue here) When importing into a folder, if an object is named after the imported one, you can not overwrite it and get an error message.
What is the new behavior (if this is a feature change)? When importing into a folder, if an object is named after the imported one, three options are proposed:
Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)