* improvement: switched from defining API key in multiple places to one place
* now generating random readings
* fix: a change in heatmap positions now updates the map accordingly
* docs: added comment to explain that the developer should use their own key
* Revert "Bump version to 1.1.0 (#671)"
This reverts commit 1603e3afea4cd0fdb88e7b5479f1f3321908afb4.
* Revert "Added feature: update heat map on data change + fix linting (#593)"
This reverts commit 1ce8726fda4cd56694680051125dd107c2817528.
* Added feature: update heat map on data change
When prop updateHeatmap is set to true --> map will rerender.
- New render of <GoogleMapReact> and data is changed, prop updateHeatmap should be true
- New render of <GoogleMapReact> and data is not changed, prop updateHeatmap should be false
* Supports multiple google map libraries + update heatmap when prop updateHeatmap equals true
* Updated this.props -> nextProps (rookie mistake...)
* Updated API documentation:
- added info about the use of other libraries in the Google Map API
- added info about the updateHeatmap prop
* Add prop `onTilesLoaded`
* (Adjust package name
* Increase version
* Make linter happy
* Remove scope from package name and reset version number
* Add description for new prop
* Remove "directories" entry
* Correct changelog
* Remove section header
* v2.0.0
* Revert version number
* Only listen to event if prop is used
Position the markers relative to the map panes.
Don't position the element that contains the markers.
Renamed all the geo service projection methods, for clarity.
Fixes an issue where, even if the end user has a proper google maps API
mock, the GoogleMaps component will throw an error when in a test
env. ReactDOM.findDOMNode(this.googleMapDom_) returns `null`.
This commit wraps the subsequent addEventListener call in an `if` block,
ensuring that an empty DOM doesn't add complications to test suites
* Use the experimental version, to get the new zoom animation.
* Don't use bounds for rendering in 3.32
* Revert the project() and unproject() methods.
Instead, add a new method fromLatLngToContainerPixel() to geo service.
* No need of setting .exp, that is by default
* Comments explaining the significance of API v3.32
* Add _VERSION to const
Added an if statement in onRemove() function that checks if "this.div" is defined before calling ReactDOM.unmountComponentAtNode(this.div). This is done to avoid throwing an "unmountComponentAtNode(...): Target container is not a DOM element" error. I ran into this error while using google-map-react with React Router and switching between tabs rapidly to stress test my application.
* Use shallowCompare to compare objects
* Use isEmpty as much as possible
* Use our own shallowEqual
* Remove fbjs
* Just disable necessary line
* Add eslint-disable where needed
* Use pure reduce and map functions
* Use only isEmpty from lodash
* Create our own isEmpty, don't use lodash
* Normalize utils names
* Group utils together
* Proper checking, better this way
* Set default value to options
* fix error about fromLatLngToDivPixel
fix "Cannot read property 'fromLatLngToDivPixel' of undefined" #257
* skip only the code that relates to div or overlay
* Revert "Fix ipad dragging issue (#233)"
Using the built in support from google maps would make the component more
mobile friendly.
This reverts commit 7d1180c5427750e18411874f538ae6bfbbe33498.
* Improve documentation around touch device support
* Fix linting errors
* Add ne and sw to bounds object
* Add ability to use ne and sw in fitBounds
* Return all corners from fitBounds
* Remove exports object in favour export
When the resize event is triggered, the original center was lost.
This issue is significant when the map is renders outside visible dom with zero height and width.
When placed into the visible dom, the resize is triggered correctly. With this change the center will persist. (Without this fix the old center is the top left corner)
