You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
It seems, that my app rerenders App component frequently in current build. Which triggers load function from YMaps provider. getPromise function works correct and maps loads only one time. But sometimes load function fired when window.ymaps is in incompleted state.
In that case
provider get ymaps in incompleted state
setApi fired again from ymaps.ready callback, but some components are already crushed, including Map component from react-yandex-maps.
Also, may be I misused withYmaps HOC.
What exactly second argument waitForApi for? Is it possible to get unready ymaps if waitForApi leaved by default, which is false?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
react-yandex-maps
4.4.0I use YMaps provider in such way
with
ns: 'ymaps'
, because it's necessary for vector maps.Strangely, in lates build of my app, this line
https://github.com/gribnoysup/react-yandex-maps/blob/master/src/YMaps.js#L41
sometimes fired before this line
https://github.com/gribnoysup/react-yandex-maps/blob/master/src/YMaps.js#L79
but ymaps isn't ready at that point.
It has only
load
,modules
,ready
,vow
and__provideBundle
.Then
ymaps
object is provided byMap
component render nothing. My custom components withwithYmaps
HOC also receives uncompleted ymaps object and crush.The text was updated successfully, but these errors were encountered: