Bugfix/17005 replacing assets via gql #17031
Merged
Conversation
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
[ci skip]
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.
Description
Issue 1:
Fixes a bug where
avoidFilenameConflictswasn’t always working as expected.For example, if you have two assets with filenames
file-one.pngandfile-two.pngand you’re replacing thefile-one.pngvia GQL mutation, the data specifies that the new filename is supposed to befile-two.pngthen the file will be uploaded, and the asset will be updated, but you’ll end up with two separate assets with files with filenamefile-two.png.Issue 2:
Trigger
Assets::EVENT_BEFORE_REPLACE_ASSETandAssets::EVENT_AFTER_REPLACE_ASSETwhen replacing an asset via GQL mutation.Related issues
#17005