Skip to content

handle getLocation null response properly

Matthias Larisch requested to merge ml-behave-nicely-with-default-location into master

Session::getLocation returns null in case there is no valid location available. Have all paths using this a proper handling. This sometimes doesn't make sense, but it is better than failing the request leading to a lot of errors in production.

e.g.

Merge request reports