fix: trigger events on metadataReplace call #377
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
fmauNeko
approved these changes
Oct 8, 2024
Kuruyia
approved these changes
Oct 8, 2024
|
do not merge please, 2-dev was not aligned when I branched |
Juiced66
force-pushed
the
fix/trigger-events-metadata-replace
branch
from
2e337d9 to
ee4f413
Compare
github-actions bot
pushed a commit
that referenced
this pull request
Oct 8, 2024
## [2.4.2-dev.1](v2.4.1...v2.4.2-dev.1) (2024-10-08) ### Bug Fixes * trigger events on metadataReplace call ([#377](#377)) ([df4b417](df4b417))
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.
Adds a triggerEvent to allow piping on
generic:document:afterWriteas it was possible before KZLPRD-323