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

use setState instead of direct assignment #3

Merged
merged 7 commits into from
Apr 9, 2019

Conversation

Simply007
Copy link
Contributor

fixes #1

We are using this component in https://github.com/Kentico/cloud-sample-app-react and it does not look good to have warnings in the sample application.

I have just change what does the react see as a best practice - the state is updating asynchronously using setState method.

@mynameistechno
Copy link

👍

@Simply007
Copy link
Contributor Author

@Chevtek, do you have any ETA when you are able to merge the fix?

@karpikpl
Copy link

karpikpl commented Apr 9, 2019

thanks for the PR, unfortunately looks like component is dead :/

@Simply007
Copy link
Contributor Author

@karpikpl, @mynameistechno, @chevex
I could publish the fixed version as a new npm package.

@mynameistechno
Copy link

Please do.

@chevcast chevcast merged commit 1b5ad08 into chevcast:master Apr 9, 2019
@chevcast
Copy link
Owner

chevcast commented Apr 9, 2019

Thanks you guys. Been going through some rough stuff for the last year and haven't had time to follow up with anything. I just merged this in and I'll publish it soon. Thanks for going the extra mile to get a fix out for everyone :)

@Simply007
Copy link
Contributor Author

🤣 I have just published the fixed version 😆
https://www.npmjs.com/package/@simply007org/react-spinners

@chevcast
Copy link
Owner

chevcast commented Apr 9, 2019

Right, hence why I'm thanking you for getting a fix out despite my absence 😉

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