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

Translating page Style and Lifecycle. #26

Closed
wants to merge 25 commits into from

Conversation

charBap
Copy link

@charBap charBap commented Mar 21, 2019

This pull request is in reference to translating "Style and Lifcycle" page.
#1

  • Style and Lifecycle
  • किसी फंक्शन को क्लास में बदलना
  • क्लास में स्थानीय state जोड़ना
  • क्लास में जीवनचक्र की विधियाँ जोड़ना
  • सही ढंग से state का उपयोग करना
  • State अपडेट्स असिंक्रोनस हो सकते हैं
  • डेटा नीचे बहती है

@netlify
Copy link

netlify bot commented Mar 21, 2019

Deploy preview for hi-reactjs ready!

Built with commit c364000

https://deploy-preview-26--hi-reactjs.netlify.com

Copy link
Member

@arshadkazmi42 arshadkazmi42 left a comment

Choose a reason for hiding this comment

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

This is great start
I have started the review.
I have added the feedback till line 60.
Once you are done fixing those, we can continue with a review of the next parts of the translation.

Please do go through the review process (here #23) which we follow.
You can make the suggested changes and add an 👍 emoji to acknowledge it, the reviewer will review the changes and they will resolve the feedback

content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
1. राज्य => State
2. प्रतिक्रिया => React
3. घटक => कौम्पोनॅन्ट
@arshadkazmi42
Copy link
Member

@charBap Can you also, mark the review feedback which you have fixed using 👍 emoji

@arshadkazmi42
Copy link
Member

@charBap Do not resolve the feedbacks, reviewer will resolve it.
Read our review process here #23
Please read my feedback review also once.

@arshadkazmi42
Copy link
Member

arshadkazmi42 commented Mar 22, 2019

@charBap Please read the comments I have been adding, it will be difficult to review if you are not reading my comments.
"Do not resolve the feedbacks." Reviewer will resolve it after verifying.
Which ever feedbacks are fixed add a 👍 emoji in the comments of that feedback

@charBap
Copy link
Author

charBap commented Mar 22, 2019

@arshadkazmi42 I have resolved all issues that you have specified.

@charBap
Copy link
Author

charBap commented Mar 22, 2019

@arshadkazmi42 Sorry my bad.

@arshadkazmi42
Copy link
Member

@charBap Do not mark them resolved, just add a 👍 in the comments.
Once you are done marking 👍 to all the feedbacks, I will start reviewing your changes

@arshadkazmi42
Copy link
Member

arshadkazmi42 commented Mar 22, 2019

It's just to follow a procedure, it will be easy for reviewers to keep track of the review if everyone follows the process

@arshadkazmi42
Copy link
Member

@charBap All changes looks fine. There is just a small issue you missed, I have left a comment for that and resolved all other conversations.
Once you update that, I will start reviewing the next parts of the translation

Copy link
Member

@arshadkazmi42 arshadkazmi42 left a comment

Choose a reason for hiding this comment

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

Great work till now.
Added few more comments, done till line 109

content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
@arshadkazmi42
Copy link
Member

@charBap There are many feedback which are not acknowledged, can you have a look at those too

@charBap
Copy link
Author

charBap commented Mar 23, 2019

@arshadkazmi42 I am doing it right now. :)

@arshadkazmi42
Copy link
Member

@charBap There is 1 issue at line 75-76, once that is fixed, I will continue with next lines review

Copy link
Member

@arshadkazmi42 arshadkazmi42 left a comment

Choose a reason for hiding this comment

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

Great work.
Added some more comments.
Done till line 250

content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
content/docs/state-and-lifecycle.md Show resolved Hide resolved
content/docs/state-and-lifecycle.md Outdated Show resolved Hide resolved
@arshadkazmi42
Copy link
Member

@charBap I have resolved most of the feedbacks, there is a couple of feedbacks which I missed in my previous review, I have added comments for those, once you are done with those we can move ahead with the review process.

@arshadkazmi42
Copy link
Member

@charBap There is one more fix pending.


The `render` method will be called each time an update happens, but as long as we render `<Clock />` into the same DOM node, only a single instance of the `Clock` class will be used. This lets us use additional features such as local state and lifecycle methods.
हर अपडेट पर `render` फंक्शन कॉल होगा, लेकिन जब तक हम `<Clock />` को एक ही DOM नोड में रेंडर करते हैं, तब तक `Clock` क्लास का केवल एक ही उदाहरण इस्तेमाल किया जाएगा। इससे हम लोकल state और Lifecycle विधियों जैसी अतिरिक्त सुविधाओं का उपयोग कर सकते हैं।
Copy link
Member

Choose a reason for hiding this comment

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

उदाहरण -> incorrect translation

Copy link
Member

Choose a reason for hiding this comment

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

दृष्टांत -> what?

Copy link
Author

Choose a reason for hiding this comment

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

Can you please suggest then what should go there. (Please specify in hindi)

@saranshkataria
Copy link
Member

done till {#adding-local-state-to-a-class}


We will move the `date` from props to state in three steps:
हम तीन चरणों में date को props से state में भेजेंगे:
Copy link
Member

Choose a reason for hiding this comment

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

भेजेंगे -> badalenge

</div>
);
}
}
```

2) Add a [class constructor](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes#Constructor) that assigns the initial `this.state`:
2) एक [class constructor](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Classes#Constructor) जोड़ें जो प्रारंभिक `this.state` को असाइन करता है:
Copy link
Member

Choose a reason for hiding this comment

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

करता है -> karega

@@ -155,9 +156,9 @@ Note how we pass `props` to the base constructor:
}
```

Class components should always call the base constructor with `props`.
क्लास के components को हमेशा बेस कंस्ट्रक्टर को `props` के साथ कॉल करना चाहिए।
Copy link
Member

Choose a reason for hiding this comment

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

translate components

Copy link
Member

Choose a reason for hiding this comment

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

revisit translation too, gramatically doesn't seem right

Copy link
Author

Choose a reason for hiding this comment

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

revisit translation too, gramatically doesn't seem right

Please suggest.


3) Remove the `date` prop from the `<Clock />` element:
3) `<Clock />` एलिमेंट से `date` prop निकालें:
Copy link
Member

Choose a reason for hiding this comment

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

date prop ko kuch aise nikale

Copy link
Author

Choose a reason for hiding this comment

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

Seems right the way it is. As "ko kuch aise nikale" is long and does not fit right.

@@ -195,17 +196,17 @@ ReactDOM.render(

[**Try it on CodePen**](https://codepen.io/gaearon/pen/KgQpJd?editors=0010)
Copy link
Member

Choose a reason for hiding this comment

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

Missed translation here

Copy link
Author

Choose a reason for hiding this comment

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

Umm where??

@saranshkataria
Copy link
Member

done till {#adding-lifecycle-methods-to-a-class}

@saranshkataria
Copy link
Member

@charBap are you still working on this?

@charBap
Copy link
Author

charBap commented Apr 17, 2019

Please ignore the previous commit. I tried to make a different pull request.

@saranshkataria
Copy link
Member

@charBap there is no such thing as ignoring a commit, you need to undo the changes

@arshadkazmi42
Copy link
Member

@charBap Any updates on this? Let us know if you need any help

@saranshkataria
Copy link
Member

@charBap let us know if you are going to complete this, else we will be closing this PR out

@saranshkataria
Copy link
Member

@arshadkazmi42 should we close this out, and wait for someone to pick it up from here, or do you want to do that?

@arshadkazmi42
Copy link
Member

arshadkazmi42 commented Dec 3, 2019

@saranshkataria Let's close this, this already have some wrong commits. We do not want to spend time on fixing that.
I already have an open PR. Will pick this up once that is closed.

Edit:

Just checked, its almost done, let me pick this up. I will do the clean up and let's get this reviewed and merged.

@arshadkazmi42 arshadkazmi42 self-assigned this Dec 8, 2019
@arshadkazmi42 arshadkazmi42 added the 2nd Review Second phrase of review label Jan 24, 2020
@arshadkazmi42
Copy link
Member

@saranshkataria I am seeing alot of conflicts also in this. Lets close this. We can open new PR for this page?

@saranshkataria
Copy link
Member

@arshadkazmi42 Sounds good. But let's keep a track of the PR in the main issue so as to someone can pick things up from where @charBap left them and that effort does not get wasted.

@arshadkazmi42 arshadkazmi42 removed their assignment Oct 20, 2022
@arshadkazmi42
Copy link
Member

Closing due to inactivity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants