Skip to content
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

min and max Date change issue #384

Open
DiligentMe opened this issue May 14, 2024 · 2 comments
Open

min and max Date change issue #384

DiligentMe opened this issue May 14, 2024 · 2 comments

Comments

@DiligentMe
Copy link

When the minDate and MaxDate is changed, it remain on previous min-max Date. When i move to actual month (previous or next) it behaves abnormally.
new min and MaxDate is newer than previous min max date, previous button stays active infinitely and same is the case with if minmax date is older than previous minmax date it next button keeps active.
When i actually move to actual minmax date month it gets set to correct min max date range.

please help to solve this problem!

@peacechen
Copy link
Collaborator

This sounds like a bug in the prop change detection @tranjog

It's time to refactor this to a function component with hooks. The prop comparison logic has gotten too complex and unmanageable.

@DiligentMe
Copy link
Author

a little more precise update about the issue

  1. it scrolls to current month even if the new min max date doesn't include the current month when i use with a key to create fresh new calander, moving to actual month it gets corrected
  2. If i don't use key, it sticks to last month on screen and when i move to the actual month it gets corrected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants