-
Notifications
You must be signed in to change notification settings - Fork 387
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
Hooks reference #226
Hooks reference #226
Conversation
Deploy preview for ru-reactjs ready! Built with commit 2d75b9e |
Deploy preview for ru-reactjs ready! Built with commit dc5a6e1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Для первой итерации ревью достаточно будет изменений. Завтра постараюсь вычитать, очень много дословного перевода.
Также рекомендую ознакомиться с соглашением по переводу.
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Предложения для улучшения перевода.
content/docs/hooks-reference.md
Outdated
> | ||
> If you're migrating code from a class component, `useLayoutEffect` fires in the same phase as `componentDidMount` and `componentDidUpdate`, so if you're unsure of which effect Hook to use, it's probably the least risky. | ||
> Если вы переносите код из компонента класса, `useLayoutEffect` запускается в той же фазе, что и `componentDidMount` и `componentDidUpdate`, поэтому, если вы не уверены, какой хук эффект использовать, это, вероятно, наименее рискованно. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
> Если вы переносите код из компонента класса, `useLayoutEffect` запускается в той же фазе, что и `componentDidMount` и `componentDidUpdate`, поэтому, если вы не уверены, какой хук эффект использовать, это, вероятно, наименее рискованно. | |
> Если вы переносите код из компонента класса, `useLayoutEffect` запускается на том же этапе, что и `componentDidMount` и `componentDidUpdate`, поэтому, если вы не уверены, какой хук эффект использовать, это, вероятно, наименее рискованно. |
Co-Authored-By: polling <sergey.bulatovich@gmail.com>
@polling пожалуйста, рассмотрите/примите предложенные правки, если у вас есть возможность |
No description provided.