Outdated scheduling in "Design Principles"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
This is a subtle distinction but a powerful one. Since you don’t call that component function but let React call it, it means React has the power to delay calling it if necessary. In its current implementation React walks the tree recursively and calls render functions of the whole updated tree during a single tick. However in the future it might start delaying some updates to avoid dropping frames.
If something is offscreen, we can delay any logic related to it. ... To be clear, we are not taking advantage of this right now.
As far as I understand, React is taking advantage of delaying updates? https://github.com/facebook/react/issues/6170#issuecomment-318204454
If that's the case, seems like this part of the docs is outdated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Find the “Design Principles” documentation page and review the quoted scheduling passages alongside the linked React issue and comment. Confirm whether the statements are outdated, then revise the affected wording to match React’s current update scheduling behavior and verify the documentation changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100