How to use fitBounds, panTo, etc about react-google-maps

[dmitry]

You can access them directly through refs, as it's shown here: #17

[tomchentw]

I took a day to rewrite the module from scratch on #88 . However, I remove these method from the component APIs. Do you guys think it's a good idea to remove it or keep it?

[LarryEitel]

I have a use case for using fitBounds. Do you expose the google map object so that it would be possible to act directly on it? Or is that philosophically improper?

[tomchentw]

It's not a easy design decision and I certainly believe exposing it is philosophically improper. But I cannot come up with a better way other than exposing getter though ...

[LarryEitel]

I would be in favor of exposing it recognizing that even though it may be improper it may be the only way to achieve something that would otherwise require scrapping the use of the project altogether. :)

[tomchentw]

Released v2.0.0 and v2.0.1.

[outdooricon]

Now with the rewrite, I'm pretty confused on what the correct way to use these is... especially fitBounds. I assume that panBounds is useless to set since I assume a new map is created every time state changes (is that right?). But setting fitBounds doesn't seem to actually work. Could you give us an example of how we should be setting the bounds? Thanks for this great project!

[tomchentw]

State changes will only be applied when you have controlled properties. Try calling fitBounds in your cDU?

[outdooricon]

isn't fitbounds a controlled property?

[tomchentw]

@outdooricon it's public APIs from the ref: http://git.io/vGc4H

[outdooricon]

Ok, I think i understand. I'm really curious what the use case of even exposing the these other properties that @LarryEitel has. It's pretty confusing to expose these if they don't really work.