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

CalendarList - fix staticHeader moves month out of range #2242

Merged
merged 2 commits into from
May 28, 2023

Conversation

Inbal-Tish
Copy link
Collaborator

@Inbal-Tish Inbal-Tish commented May 28, 2023

The arrow press should stop passing months in the static header when getting to the end of the past/future scroll range.

To test: in the horizontal CalendarList screen change the past/futureScrollRange prop to 0 or a small number and press the arrows to move btw months - when you get to the edges you can see the months in the header changing but the calendar is off - the months should not change at all. This PR fix this bug.

Copy link
Collaborator

@ethanshar ethanshar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. wrote a small comment.
Btw, the description was really helpful 🙏

Comment on lines 47 to 48
pastScrollRange={RANGE}
futureScrollRange={RANGE}
pastScrollRange={0}
futureScrollRange={12}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did u leave this on purpose?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No... Fixed

@Inbal-Tish Inbal-Tish merged commit caa0ab6 into master May 28, 2023
1 check passed
@Inbal-Tish Inbal-Tish deleted the fix/CalendarList_staticHeader_range branch December 7, 2023 08:43
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

Successfully merging this pull request may close these issues.

None yet

2 participants