Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
This plugin is already quite good. But IMHO it still misses a few things to be a full fletched alternative to cordova-plugin-googlemaps in production.
I like to propose the following issues to be added to a possible milestone for v2.0 of this package. I considered a major release tag since some of the changes below are braking to ‘old’ API.
- The API should be unified to be completely the same on Android and iOS. At the moment event listeners and API calls have different names on both platforms. They should be the same.
- (#8) Plugin classes should be split up in multiple classes
- Multiple map instances should be possible at once. The point above simplifies this. I already have a working proof-of-concept for Android.
- (#15 & #44) Custom marker icons should be refactored to be fully supported and support vectors (and when possible svg’s, but I do not think that is a hard requirement).
- (#84) It should be possible for HTMLElements to overlap the map.
- Ideally, support for custom info windows is added. It would be even more interesting to support html content as an info window.
- Documentation should be updated. It should also be more clear. (#17 & #4) have a WIP on these but slow progress.
- (#2 & #3) Finish drawing methods. Working local prototypes, need to cleanup and push. Could be a part of v2.
When above issues are addressed it is pretty much on par with the cordova maps, I think. Also, point 1, 2 and 3 I am already working on.
What do you think about this? Do you have any other important issues in mind that should be addressed?
__
On a side note: when releasing v2.0, it might be a good idea to change the name to capacitor-community/google-maps. This change addresses possible confusing about “capacitor” being two times in the name. Above all, the omitting of the word “native” opens up possibilities to also support web in the future.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:13
- Comments:23 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Awesome news: a (pretty stable) beta version 2 has been released to npm under the name
@capacitor-community/google-maps. Extensive documentation can be found here: https://capacitor-community.github.io/google-maps/Progress can be seen here: https://github.com/DutchConcepts/capacitor-google-maps/tree/next
New API proposal: https://github.com/DutchConcepts/capacitor-google-maps/blob/next/API_REFERENCE.md