-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add a log action for copy_for_translation operation #7352
Conversation
Manage this branch in SquashTest this branch here: https://kaedrohocopy-for-translation-l-ip5wi.squash.io |
b68123d
to
a22fb76
Compare
Currently, when a user copies a page for translation, the 'copy' log action is used. This adds a more specific 'copy_for_translation' operation to be used instead when the user is translating.
a22fb76
to
ceb306e
Compare
@@ -71,6 +71,7 @@ Action Notes | |||
``wagtail.rename`` A page was renamed | |||
``wagtail.revert`` The page was reverted to a previous draft | |||
``wagtail.copy`` The page was copied to a new location | |||
``wagtail.copy_for_translation`` The page was copied into a new locale for translation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought... any reason not to follow the hierarchical pattern of the other action names, and make it something like wagtail.copy.for_translation
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems a bit inconsistent though. For example wagtail.revert
is a type of edit, and wagtail.publish.schedule
is not publishing the page, just scheduling it. I like the idea of encoding the hierarchy in the names though, maybe we could fix these?
Currently, when a user copies a page for translation, the 'copy' log action is used. This adds a more specific 'copy_for_translation' operation to be used instead when the user is translating.
Merged in bea17ac. |
Currently, when a user copies a page for translation, the 'copy' log action is used.
This adds a more specific 'copy_for_translation' operation to be used instead when the user is translating.