You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.
#147
Closed
ayushbafna24 opened this issue
Jan 20, 2021
· 5 comments
Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state
Please update the following components: Rating, RatingAPILayer
The text was updated successfully, but these errors were encountered:
There is an exact issue like this already #146 . Please check it out. It is marked as help wanted. I'm busy now with other stuff so any pull request is really welcome.
On Thu, Jan 21, 2021, 3:05 PM dreyescat ***@***.***> wrote:
There is an exact issue like this already #146
<#146> . Please check it
out. It is marked as help wanted. I'm busy now with other stuff so any pull
request is really welcome.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#147 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC4PYN22OB6S4HCZW4LZUS3S27YPXANCNFSM4WKOZTHA>
.
You do not need to depend on me. Just fork the repo and you will have a copy of your own where you can do whatever you consider fits your needs. Then, afterwards, if you want, you can create a pull request.
Check this if you are not really sure what a fork and pull request are.
Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.
Please update the following components: Rating, RatingAPILayer
The text was updated successfully, but these errors were encountered: