fix: refresh slots when timezone changes with restriction schedule #26977
+25
−0
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 does this PR do?
Fixes an issue where available time slots were not refreshed when the user changed the timezone for events that use a restriction schedule.
Previously, changing the timezone updated the UI timezone but did not invalidate and refetch the schedule data, causing stale or incorrect slots to be displayed. This PR ensures the schedule is invalidated and refetched when the timezone changes, only when
useBookerTimezoneis enabled and a restriction schedule is present, avoiding unnecessary network requests.Visual Demo
Before
After
(Screenshots / video can be added if required)
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
useBookerTimezoneis enabled for the eventExpected Result
Checklist