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 }}
Repository navigation
Timeline: error on init when the nearest time values contain an empty value #13163
When the Timeline works with a range, at startup it asks for the first and the last value of the time domain with two requests, to set the initial range. When one of them fails or returns no value, the initialization throws Cannot read properties of null (reading 'split') and stops: the current time and the range are not set from the data of the layer.
updateRangeOnInit in web/client/epics/timeline.js splits every value before removing the empty ones.
How to reproduce
Open a map with a layer with the time dimension and the Timeline configured to start with a range (e.g. initialMode: "range"), where one of the two GetDomainValues requests sent at startup fails (or returns no value)
Wait for the Timeline to initialize
Expected Result
The range of the Timeline is initialized using the available value.
Current Result
The error above is logged in the browser console (Error in epic "setRangeOnInit") and the range is not initialized, so the Timeline is not positioned on the data of the layer. The rest of the application keeps working.
Not browser related
Other useful information
TypeError: Cannot read properties of null (reading 'split')
at updateRangeOnInit (web/client/epics/timeline.js)
Activity