refactor: simplified isDateInRange func to improve large calendar lis… #2398
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zkteco-home
approved these changes
Jan 24, 2024
|
Great! Currently having issues rendering a calendar with more than 3 months of lookahead, without getting framedrops. So anything that makes re-renders faster would be really helpful! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When debugging to improve performance for a large calendar list ( eg. 15 months calendar list ), we found the
isDateInRangenot super optimize as we needed to complete some not-necessary loop action for each month each time we scroll through the calendar list.isDateInRangeisDateInRangeAs you can see, we can get rid of the
not-necessary loop action