Closed MuresanSergiu closed 3 months ago
Feel free to submit a PR to fix this, seems like you know where to fix this, right?
Is this issue still relevant? Can I close this?
Did it get fixed? I haven't had the time to push a fix for this and currently I'm using a workaround...
If it's not important enough for you to fix it then I'll be closing this issue. Feel free to submit a PR any time you want 😃
But the issue still exists... That's kinda disingenuous, don't you think?
It's very hard to understand the issue from the description. I haven't encountered it. While I don't argue that there is an issue, apparently it's not important enough for anyone to fix it, so there's no reason to keep this issue open. If anyone in the future will encounter it and would like to fix it I can always link to this issue.
If you "don't argue that there is an issue" then don't close it. Do issues only exist for those that have the problem AND are willing to fix it? No, of course not.
I didn't know it was difficult to understand the issue, but I would expect people to at least ask before closing it. I would gladly give a more in-depth explanation.
I'm deeply disappointed in this type of behavior.
This seems to happen in the MarkerComponent class because the ngOnChanges handler doesn't check if markerInstance has been assigned accessing 'setLngLat' of undefined. The crash is inconsistent to replicate
Using latest release: 17.4.1 in Angular 17