-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Issues when duplicating a component #10896
Comments
Indeed, only a few of the settings are currently cloned: weblate/weblate/trans/views/create.py Lines 516 to 524 in 3ce0a3d
More of them can definitely be added. |
This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this. You can learn about how to get started in our contributors documentation. |
@nijel I've included the requested information in duplication in #11079. Let me know if there's any other attribute that should be included for duplication. Regarding the duplication functionality, should we consider showing the duplicate icon from the all components list page of a project? If so, what specific functionalities and attributes should be included in the duplication process? |
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the problem
Creating a component that's a copy of another component feels more difficult than it needs to be.
Describe the solution you would like
a. The license
b. The contributor agreement text
c. The commit messages
These all have to be manually copied from an existing component to the new component.
I'd make it more obvious that duplication is possible with a copy icon (e.g,. something like https://www.flaticon.com/free-icon/copy_126498?term=copy&page=1&position=2&origin=tag&related_id=126498) next to the existing "browse" icon.
The lack of duplication of the other settings feels like a bug.
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: