For collaborators: There is currently only several main components refactored to new React APIs about react-google-maps-api HOT 15 CLOSED

@urikphytech welcome onboard

from react-google-maps-api.

@JustFly1984 Thanks! I prefer using my personal account for OSS. Can you invite @uriklar to be a collaborator instead of this account? Thanks!

from react-google-maps-api.

@uriklar done

from react-google-maps-api.

@uriklar so in this case just don't commit your google API key), and lets coordinate features we are working on.

from react-google-maps-api.

Thanks! @JustFly1984 I sent you an invite on google hangouts. We can chat there. I'd be happy to have a chat about roadmap, open issues etc...

from react-google-maps-api.

There is components left to refactor to new API

LoadScript - done
GoogleMapProvider - done
GoogleMap -done
TrafficLayer - done
BicyclingLayer - almost done, there is a bug, which errors out onload.

Circle - not done
Marker - not done
Polyline - not done
Polygon - not done
Rectangle - not done
InfoWindow - not done
OverlayView - not done
DirectionsRenderer - not done
FusionTablesLayer - not done
KmlLayer - not done
StreetViewPanorama - not done

from react-google-maps-api.

Now I will continue with
OverlayView
DirectionsRenderer
FusionTablesLayer
KmlLayer

from react-google-maps-api.

Ok, so i'll take shape components:
Polyline
Polygon
Rectangle
Circle

from react-google-maps-api.

Thanx
Them you do examples, just add one more < GoogleMapProvider /> to index.js, and you can comment out first 2 temporary, so it does not heat up your CPU

from react-google-maps-api.

@JustFly1984 I see that you're creating the google maps instances in the constructor. This will create a bug when using StrictMode (and later on ConcurrentMode)
See this issue I opened on react-google-maps, it's explained in details there by alexrussel:
tomchentw/react-google-maps#921

The solution is to create the component instance in cDM. The downside of this is that you then have to call setState in cDM... Maybe you can think of a better solution for this.

from react-google-maps-api.

@JustFly1984 also, can you give me a brief explanation as to why you are using the prevProps in derived state? What use case does it solve for you?

from react-google-maps-api.

from react-google-maps-api.

@uriklar Ok, so I've read all of this) and here is my thoughts - lets finish up current implementation first,
And after that you can create separate example with StrictMode and test it out. Currently I have made a lot of changes to original API, so it could fix itself, or not. I'm pretty sure I'll find the way to handle this issue.

from react-google-maps-api.

A little off topic: What do you think about switching the bundler from webpack to rollup? if there any benefits? I want to support as many platforms as possible

from react-google-maps-api.

Current progress:

LoadScript - done
GoogleMap -done
TrafficLayer - done
BicyclingLayer - done

Circle - done
Marker - add support for MarkerCluster
Polyline - done
Polygon - done
Rectangle - done
InfoWindow - done
OverlayView - done
DirectionsRenderer - done
FusionTablesLayer - not done
KmlLayer - ?
StreetViewPanorama - not done

addons: do we really need it?

from react-google-maps-api.