This repository was archived by the owner on Jul 19, 2025. It is now read-only.
Avoid passing anonymous functions as props #157
Merged
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This PR aims to remove passing anonymous functions as props.
When passing anonymous arrow function as a prop - new function is created every time component is rendered, so if it's passed to
PureComponent-shouldComponentUpdatewill returntrueevery time.Also, often anonymous arrow functions use closure, which may cause performance issues.
Here's what changed:
Yearcomponent with simple API, used byYearSelectionreffor scrolling to selected year instead ofdocument.getElementsByClassNameDayandDayWrappercomponents with simple API, used byCalendar