Adding 'copy' action to the resource template browser. #1501
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.
This patch allows the user to copy an existing resource template.
Use case:
Imagine you have some resource templates and now are going to create a new one. Typically your templates may share some properties - 'author', 'containedIn', 'dateCreated', etc, etc. Some of them may be private and/or mandatory. Creating a new template from scratch is annoying and often causes human errors. Export-and-Import could solve the problem, but not smart.
How to use it:
You'll see copy icons beside edit icons in the resource template list as following:
Click the icon and you'll be directed to the form of the new template that is copied from the original template.
Note:
This patch does not provide any API for copying action. IMHO, in the case of API-based operation, GET-and-POST is enough for typical use cases.