Skip to content

docs: fix confusing useMemo initial render wording (fixes #7752)#8528

Draft
LuxologyGG wants to merge 1 commit into
reactjs:mainfrom
LuxologyGG:fix/auto-issue-7752
Draft

docs: fix confusing useMemo initial render wording (fixes #7752)#8528
LuxologyGG wants to merge 1 commit into
reactjs:mainfrom
LuxologyGG:fix/auto-issue-7752

Conversation

@LuxologyGG

Copy link
Copy Markdown

The Returns section of the useMemo reference stated that React calls calculateValue "with no arguments," which reads as if the memoized computation itself takes no inputs even though examples pass dependencies.

Removed the redundant "with no arguments" phrase so the initial-render description matches the Usage section below it.

Before:

On the initial render, useMemo returns the result of calling calculateValue with no arguments.

After:

On the initial render, useMemo returns the result of calling calculateValue.

Closes #7752

@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

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.

[Typo]: explanation of useMemo first-render return value, doesn't make logical sense

2 participants