fix: use TSiblingData for previousSiblingDoc in FieldHook
#14503
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
Contributor
|
🚀 This is included in version v3.63.0 |
zubricks
pushed a commit
that referenced
this pull request
Nov 10, 2025
### What? In field hooks, `previousSiblingDoc` is typed as `TData`. ### Why? This value should actually be typed as `TSiblingData`, I've confirmed the sibling data is actually what is returned when a field hook runs. ### How? Updated `FieldHook` typing, as well as `RichText` field hook typings Fixes #9735
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
In field hooks,
previousSiblingDocis typed asTData.Why?
This value should actually be typed as
TSiblingData, I've confirmed the sibling data is actually what is returned when a field hook runs.How?
Updated
FieldHooktyping, as well asRichTextfield hook typingsFixes #9735