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

Sharing state between components 번역 #398

Merged
merged 2 commits into from Dec 30, 2021
Merged

Sharing state between components 번역 #398

merged 2 commits into from Dec 30, 2021

Conversation

devSoyoung
Copy link
Contributor

@devSoyoung devSoyoung commented Dec 19, 2021

Copy link
Member

@hg-pyun hg-pyun left a comment

Choose a reason for hiding this comment

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

기여 감사합니다. 좀 다듬으면 좋은 문장들을 suggestion으로 달아보았습니다 🙇‍♂️


To lift state up, you must locate the closest common parent component of *both* of the child components that you want to coordinate:
state를 올리려면 조정하려는 *두* 자식 컴포넌트의 가장 가까운 공통 부모 컴포넌트에 두어야 합니다.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
state를 올리려면 조정하려는 ** 자식 컴포넌트의 가장 가까운 공통 부모 컴포넌트에 두어야 합니다.
state를 올리려면, 조정하려는 ** 자식 컴포넌트의 가장 가까운 공통 부모 컴포넌트에 두어야 합니다.

@@ -397,17 +397,17 @@ label { display: block; }

</Solution>

### Filtering a list {/*filtering-a-list*/}
### 목록 필터링 {/*filtering-a-list*/}
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
### 목록 필터링 {/*filtering-a-list*/}
### 목록 필터링하기 {/*filtering-a-list*/}


Your app will change as you work on it. It is common that you will move state down or back up while you're still figuring out where each piece of the state "lives". This is all part of the process!
작업하면서 애플리케이션은 계속 변합니다. 각 state가 어디에 "생존"해야 할지 고민하는 동안 state를 아래로 이동하거나 다시 올리는 것은 흔히 있는 일입니다. 이건 모두 과정의 일부입니다!
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
작업하면서 애플리케이션은 계속 변합니다. 각 state가 어디에 "생존"해야 할지 고민하는 동안 state를 아래로 이동하거나 다시 올리는 것은 흔히 있는 일입니다. 이건 모두 과정의 일부입니다!
작업이 진행되면서 애플리케이션은 계속 변합니다. 각 state가 어디에 "생존"해야 할지 고민하는 동안 state를 아래로 이동하거나 다시 올리는 것은 흔히 있는 일입니다. 이건 모두 과정의 일부입니다!


To see what this feels like in practice with a few more components, read [Thinking in React](/learn/thinking-in-react).
컴포넌트를 몇 개 더 사용하면 어떤 느낌인지 알아보려면 [React로 사고하기](/learn/thinking-in-react)를 읽어보세요.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
컴포넌트를 몇 개 더 사용하면 어떤 느낌인지 알아보려면 [React로 사고하기](/learn/thinking-in-react)를 읽어보세요.
컴포넌트를 몇 개 더 사용하여 어떤 느낌인지 알아보려면 [React로 사고하기](/learn/thinking-in-react)를 읽어보세요.

@hg-pyun hg-pyun added needs author response Changes requested needing author's input and removed beta labels Dec 20, 2021
@devSoyoung
Copy link
Contributor Author

리뷰 감사합니다 :) 제안해주신 내용 모두 반영했습니다. 덕분에 문장이 더 깔끔해졌네요! 😊👍🏻

Copy link
Member

@hg-pyun hg-pyun left a comment

Choose a reason for hiding this comment

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

LGTM

@hg-pyun hg-pyun added ready to merge push the merge button :) and removed needs author response Changes requested needing author's input labels Dec 27, 2021
@hg-pyun hg-pyun merged commit 45cb2cf into reactjs:main Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to merge push the merge button :)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants