12 Replies
Why I cannot fking assert and tell that IT REALLY HAS A FUKING REF?
im about to cry tbh, spending an entire week coding this, trying to deploy and now im being forced to follow this kind of dumb rules
Im using an old AF library, not updated, I need to save the actual created <Marker /> so I can execute a openPopup later on
IT WORKS PERFECTLY ON LOCAL; WHY TF I CAN'T DEPLOY IT OUTSIDE?
is this the react-google-maps/api library or im just reaching? coz the the markers api from google maps is being deprecated and and may be no longer supported
nah
react-leaflet
to simplify things..............
Main Leaflet file loads the map,
EnemyCamp component creates dynamically the enemy bases of the map
----
I need to execute .openPopup() on the Markers created, but I have issues "saving" them
and this is where I have a lot of problems
React-leaflet is shit.
I also tried to use it for something but it just is stupid in any way possible
I was about to directly use an external <script /> and just use leaflet and javascript
but i thought it'd worse
true
also my lack of proper knowledge about how to save the ref of each marker that is being created by a map
x.x
yes, that is sooo stupid. i hate leaflet, but there is no better alternative sadly