[Beta] Suggest/referencing values with refs

[gsong]

Is there a reason we need the input to be controlled?

[github-actions]

Size Changes

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

This PR introduced no changes to the javascript bundle 🙌

[gaearon]

thanks, but the Prettier changes are not needed. can you please undo them so I can see what you're changing?

we don't run Prettier on Markdown

[gsong]

@gaearon Formatting the code according to the .prettierrc in the repo. The changes are in a separate commit: 3c12750

[gaearon]

sorry, I don't know how to configure prettier correctly, but we don't run it on Markdown

[gsong]

@gaearon No worries, I'll configure it to ignore markdown with another PR, and update this one accordingly.

[gsong]

sorry, I don't know how to configure prettier correctly, but we don't run it on Markdown

Content markdown ignored in #5098

[gsong]

thanks, but the Prettier changes are not needed. can you please undo them so I can see what you're changing?

we don't run Prettier on Markdown

I've forced pushed up just a single commit with the proposed changes.

[eps1lon]

The problem here is that this example reads from a ref during render. Even if that specific prop is only relevant once, the overall pattern is still problematic. React might even warn if defaultValue changes. But the biggest problem is reading from a ref during render which we probably shouldn't showcase.