Open abb438 opened 9 months ago
i have the same problem how we can use Market now?
I have the same issue.
Instead of loading weekly
, quarterly
or other Google Maps API version, choose the last one in which Marker was still available: 3.55
.
It's probably a good idea to lock to a specific Google Maps API version anyway, unless you're gonna be actively and continuously maintaining the app you're building.
The version that can be specified and used will also be updated (am I right?). I feel that specifying and using 3.55 is not a fundamental solution. My project needs to be maintained, and I guess I will have to rewrite it to the official library or incorporate the vanilla js into react...
I don't think you're right. This would pretty much defeat the point of versioning.
The fact that versioning exists and has it's uses doesn't mean that it is the best long term solution. I'm with @abb438 on this one, the new version of the API should be supported to ensure long term support.
https://developers.google.com/maps/documentation/javascript/versions Choosing a version number Specify a version by number only if you regularly test and update your application. This is because numbered versions are eventually deleted as new versions are created every quarter. You can specify the version number by loading the Maps JavaScript API with the following script tag: ーーーーー I interpret this statement to mean that the version that can be specified and used will also be updated at some point, am I wrong? If I'm wrong, I'm sorry.
Hi there! Did someone find a solution for this?
Thanks!
The Marker class should continue to work and be available in all versions of the JS API (the warning message should not have been translated, which caused confusion because translations converted "deprecated" to "discontinued" and "no longer available"). At this time there is no plan to decommission the Marker class. Please see this migration guide for converting from Marker to Advanced MarkerElement if you wish to convert.
https://developers.google.com/maps/documentation/javascript/advanced-markers/migration
I didn't expect to get an explanation from you, who belongs to google, thank you! However, while I understood what you explained, I could not find any source to back it up. Still the warning has not been rescinded either. However, I am sure that is the case because I am still able to use "Marker" even after the deadline written in the warning. Can I take your statement as an official statement?
Looking at the documentation, it doesn't look like google.maps.Marker is going to be discontinued at this time!
You have to create AdvancedMarker, or wait for somebody else creating it and providing PR. This is opensource. If you really need it, but can't do it yourself, I'm open for donations crowdfunding. After I get 500$ on opencollective I can find the time to implement it.
Can anyone resolve this issue?
Can anyone resolve this issue?
https://github.com/JustFly1984/react-google-maps-api/issues/3250#issuecomment-2040911673
Hello everyone, I am having the same warning, did anyone find a fix for this?
use MarkerF
Marker will be discontinued on February 21, 2024. Please use google.maps.marker.AdvancedMarkerElement instead. For more information about the end of support, please visit https://developers.google.com/maps/deprecations.
"@react-google-maps/api": "^2.19.3",
When I looked at the console, I saw the above. (The wording may be slightly different because I am translating it into English) What should I do?
The author wrote that he is no longer interested in this library, but what is everyone going to do if the googlemapsApi spec is changed thereafter? The official google library for react is still barely documented and has not been officially released yet.
Please forgive the poor English as I am using translation software to write the text.