Open
Conversation
This task automatically removes specific order tag(s) when orders are closed/archived.
Collaborator
|
@timdmackey I agree that it might make more sense to have a single task to handle this for orders. When an existing library task is updated by adjusting any of the task options, merchants will not be able to update the task with one click, but it isn't overly onerous I think to install a fresh copy if the enhancements are useful. If you decide to update the original, then I would also recommend doing a tag check on the order before running a potentially unnecessary tag remove mutation. |
tekhaus
reviewed
Dec 9, 2025
Collaborator
tekhaus
left a comment
There was a problem hiding this comment.
Let me know what you decide on merging with original task.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Canny Request Another low-hanging fruit. The code is almost identical to Untag orders when paid.
I'm wondering if this would make sense to fold into the first task rather than having a separate task? It would have a radio select to determine which event to act on (paid, archived, fulfilled?...). I don't know how task migration works though, so it might not be possible to add those options to a task that's already installed in stores.