Opening a could save doesn't show the current base map about site HOT 4 CLOSED

This is not easy to reproduce, seems like some sort of race condition.
From what I can tell, the cause of this might be that the layer changes before it finishes loading.
I think it happens when opening a could save the AddBaseLayer is called and right afterwards UpdateBaseLayer which both change the presentation in the map of the same layer...
Need to investigate more...

from site.

Seems like the ngOnChanges is called twice on the base layer:
First time from IHM to open topo, and the next from open topo to itself due to the ID change after saving the layer in the server.
The issue is that remove is called in the on changes before the create layer finishes, apparently, not sure though, this will need to be tested I think.

from site.

This is still not solved, the problem is a race condition between ngInit and ngOnChanges... :-(

from site.

The solution was to add a queue and synchronize the calls using this queue.

from site.