Learn / Referencing Values with Refs

[piotr-pajak]

Translation of the page Learn / Escape Hatches / Referencing Values with Refs into 🇵🇱 .

Note

This is my first translation, any feedback or suggestions for improvement would be greatly appreciated 😉

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
pl-legacy-reactjs-org	⬜️ Ignored (Inspect)	Visit Preview		Apr 8, 2025 9:22pm

[dawidsabat]

In general very fast and very good translation! Nice start! 🚀

There are minor things to correct, nothing serious. Don't be scared about number of suggestions. I have a keen eye for details. This is nothing personal 😉

[piotr-pajak]

In general very fast and very good translation! Nice start! 🚀

There are minor things to correct, nothing serious. Don't be scared about number of suggestions. I have a keen eye for details. This is nothing personal 😉

Thanks for the extensive feedback! I missed quite a few things, especially regarding the impersonal form of verbs. Your feedback also answers many of the questions that I had during the translation process.

I'll apply the feedback in the next few days and will mention you once the changes have been implemented.

I also have a quick question about resolving conversations: what's the preferred approach on this repository? Should the reviewer resolve them, or the person who implements the fixes 🤔?

[dawidsabat]

That's the spirit! 🔥

I am not aware of any specific way of working in this project regarding resolving conversations, but I would say that if you simply agree with suggestion or fix is very simple and it can be done in one way only, you can apply it and resolve. I think this will be 95% of cases.

You can left conversation open in rare cases when change can be done in couple of ways and you are not sure how it will be received by the reviewer.

[piotr-pajak]

Hey @dawidsabat,
Feedback applied. Can you let me know if it's all good now?
If yes, I'd like to reserve the translation for Escape Hatches / Manipulating the DOM with Refs 😉

[dawidsabat]

Hey @dawidsabat, Feedback applied. Can you let me know if it's all good now? If yes, I'd like to reserve the translation for Escape Hatches / Manipulating the DOM with Refs 😉

Great! I will review it tomorrow.
Reservation done 😉

[dawidsabat]

Almost there. Last issues to fix and we are go for merge 😉

[github-actions]

Size changes

📦 Next.js Bundle Analysis for react-dev

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

Five Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/404	106.5 KB (🟡 +15 B)	210.88 KB
/500	106.5 KB (🟡 +15 B)	210.88 KB
/[[...markdownPath]]	108.34 KB (🟡 +15 B)	212.71 KB
/errors	106.71 KB (🟡 +15 B)	211.09 KB
/errors/[errorCode]	106.69 KB (🟡 +15 B)	211.07 KB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[dawidsabat]

Everything is fine, good job! 🚀