[leafletOptions] binding does not take into account data source updates For example, if we consider a signal-type options source that provides locations with their GPS coordinates (LatlngLiteral[]), and we subsequently update the signal by adding other GPS coordinates, the latter will be added, but when we decide to create markers on the map corresponding to these coordinates, only the default coordinates of the original signal are considered.
However, when you change the [leafletOptions] class to [leafletLayers], it takes updates into account. That said, [leafletOptions] is a misleading name, as it is supposed to take modifications into account.
[leafletOptions] binding does not take into account data source updates For example, if we consider a signal-type options source that provides locations with their GPS coordinates (LatlngLiteral[]), and we subsequently update the signal by adding other GPS coordinates, the latter will be added, but when we decide to create markers on the map corresponding to these coordinates, only the default coordinates of the original signal are considered.
However, when you change the [leafletOptions] class to [leafletLayers], it takes updates into account. That said, [leafletOptions] is a misleading name, as it is supposed to take modifications into account.
stack version: @asymmetrik/ngx-leaflet": "^17.0.0", "leaflet": "^1.9.4", "@angular/cli": "^17.3.1",