* 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
* Documentation: added PropTypes for heatmap prop
This PR improves the documentation of the heatmap prop by adding types.
I don't mind adding PropTypes validation to this prop as well if you are interested in that.
* Update API.md
I added some spacing between the interface and the example snippet.
I also added a link to the example I wrote for the other repository. I think we should delay this PR until that example is live. That way, the new Demo link will go to live functioning code rather than no where.
* 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.
This includes:
- #655 Add math abs to avoid negative values when calculating zoom
- #656 Pass map instance to onDrag handler
- #593 Added feature: update heat map on data change + fix linting
* 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.
Because the parent node of marker has size 0x0, top 50% and right 50% would affect nothing. You only need to translate(-50%, -50%) to move it to the right position.
