-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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: issue 2536 #2545
fix: issue 2536 #2545
Conversation
Loading your changes in Storybook, if I go to the onSelectSlot story and begin a selection, it immediately changes it to begin at the beginning of the day up to my selection point. |
This is an issue that exists in version 1.11.1 and is not caused by this commit. |
@forceddd You are correct, but it was your previous PR that appears to have introduced this issue in the first place. |
@cutterbl This bug should have existed a long time ago. The issue 2290 seems to be the bug described. |
@forceddd Thanks for looking into this. An you are partly right. That issue you pointed out was for dragging up. Now it is also doing it even if dragging down (which was not an issue before your change). |
@cutterbl After each 2024-04-01.10.58.23.mov |
@cutterbl Would you please check this PR again? I submitted some new file changes.I think now this PR should be able to solve these related problems. |
This is a commit to fix issue 2536 and 2529.
When I was fixing 2529, I declared
slotMetrics
as a global variable, which caused allDayColumn
instances to use the same instance ofslotMetrics
. This is also the reason why bug issue 2536 appears.In this commit, I only modified the update timing of slotMetrics.Now both issues are resolved!
2024-03-25.15.36.56.mov