Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

google map library not found! #22

Closed
kurtobando opened this issue Feb 9, 2021 · 2 comments · Fixed by #24
Closed

google map library not found! #22

kurtobando opened this issue Feb 9, 2021 · 2 comments · Fixed by #24
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@kurtobando
Copy link

Hello author,

Issue:
google map library not found!

Behavior:
The said error returns if I call GMapify component twice from a functional component.

Screenshot:
image

@krishpe
Copy link
Contributor

krishpe commented Feb 11, 2021

@sandeep-r-bharatpe

@sandeep-r-bharatpe
Copy link
Contributor

sandeep-r-bharatpe commented Feb 15, 2021

@kurtobando Thanks for notify us for this issue, we will give enhancement to inject g-mapify more then one time.

@sandeep-r-bharatpe sandeep-r-bharatpe modified the milestone: 2.2.1 Feb 15, 2021
@krishpe krishpe mentioned this issue Feb 17, 2021
krishpe added a commit that referenced this issue Feb 17, 2021
* Release V1.3.0

* Update README.md

* Update package.json

* Release V1.4.0 (#15)

* Search map updated, Marker changed

* 1.4.0 Release

* Lib updated

* Minor changes

(cherry picked from commit 89ec3ce)
(cherry picked from commit 0367cad)

* - marker position issue when map zoom in : Solved (#20)

- added *route* and *streetNumber* properties on AddressFormatter method

* fix: g-mapify fail on initialisation twice [#22] (#23)

Co-authored-by: krishpe <krish@bharatpe.com>
Co-authored-by: krishpe <64515207+krishpe@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants