Skip to content

#172 improvement: Allow Google HOC to be initialized from props #178

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

Merged

Conversation

rangoo94
Copy link
Contributor

@rangoo94 rangoo94 commented Apr 6, 2018

Hi,

It's just improvement for #172, which is also updating input when changes to props may affect component options.

@rangoo94 rangoo94 changed the title #172: Allow Google HOC to be initialized from props (improvement) #172 improvement: Allow Google HOC to be initialized from props Apr 6, 2018
@auser
Copy link
Contributor

auser commented Apr 6, 2018

This looks great! Do the examples still work?

@rangoo94
Copy link
Contributor Author

rangoo94 commented Apr 6, 2018

I just tested it and it had a single warning with setState. I fixed it now, everything should be backward compatible.

@auser auser merged commit 0137a67 into fullstackreact:master Apr 7, 2018
@mruoss
Copy link
Contributor

mruoss commented Apr 9, 2018

Hey there - Does this actually work for you? I tested the new version 2.0.0, changing the language via props. However, the map does not change its language. Do we need to re-initialize something more?

@rangoo94
Copy link
Contributor Author

Hey @mruoss, I will have time in the evening, so I will check it out deeply.

@mruoss
Copy link
Contributor

mruoss commented Apr 11, 2018

Thanks @rangoo94. I had a quick look but did not have time to dig deeper. I guess the problem is that the ScriptCache does not re-fetch the resources from google after the config changes.

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

Successfully merging this pull request may close these issues.

4 participants