-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy pasting Body instance #3326
Comments
Alternatively when copying body, we just copy the contents of the body and show toast (copied body contents, because body can not be copied) Then there is no need for confirmation dialog and its all much simpler |
Easier approach for sure and better than what is there. Downside is vars won't copy over and I place my vars almost exclusively on the body. Still would rather have any of these options above than none. |
alternatively we could copy whole page along with body |
We will need this in any case. The problem with copying body is that it feels very natural to copy the root node and paste it somewhere else. Its super unnatural to have to create a Box inside body just so one can copy the entire thing. People will always intuitively go create a page first, then go to some template and try copy the body. |
it is also unnatural when paste deletes something |
Yes, we won't be deleting anything unless user explicitely agrees |
As a user I want to be able to copy/paste the entire body contents, because usually people put instances inside the body, not an extra box for copy pasting.
Problem has been so far that we don't know how to merge 2 bodies and there can be only one in the end.
Solution: ask the user in a dialog: Do you want to use the new body or keep current one? [new] [current][abort]
Now when user selects new one, we are overriding. If user picks the old one - we are inserting the contents of the new body inside the old body.
The text was updated successfully, but these errors were encountered: