-
Notifications
You must be signed in to change notification settings - Fork 25.8k
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
fix(core): Fix nested timer serialization #59173
Conversation
There were type mismatches and or unintended any types that were preventing nested timers from accessing the delay value during hydration annotation processing.
ab48689
to
beb314f
Compare
@@ -484,13 +484,13 @@ function serializeHydrateTriggers( | |||
DeferBlockTrigger.Viewport, | |||
DeferBlockTrigger.Timer, | |||
]); | |||
let triggers = []; | |||
let triggers: (DeferBlockTrigger | SerializedTriggerDetails)[] = []; |
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.
this array was seen as any
, which is why this explicit typing is needed here.
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.
Looks great, thanks @thePunderWoman 👍
This PR was merged into the repository by commit cf89f14. The changes were merged into the following branches: main, 19.0.x |
There were type mismatches and or unintended any types that were preventing nested timers from accessing the delay value during hydration annotation processing. PR Close #59173
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
There were type mismatches and or unintended any types that were preventing nested timers from accessing the delay value during hydration annotation processing.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?