Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Learn / Referencing Values with Refs #511

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

piotr-pajak
Copy link

@piotr-pajak piotr-pajak commented Mar 22, 2025

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 😉

Copy link

vercel bot commented Mar 22, 2025

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

Copy link
Collaborator

@dawidsabat dawidsabat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Author

piotr-pajak commented Mar 27, 2025

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
Copy link
Collaborator

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
Copy link
Author

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
Copy link
Collaborator

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 😉

Copy link
Collaborator

@dawidsabat dawidsabat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

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.

2 participants