The desktop app contains a caching mechanism that automatically caches network requests on a per-URL and per-data-object status. However, the URL that's being used to communicate with the Docker containers is always the same (even if the underlying database is different). This means that some requests are wrongly being re-used. This PR fixes this by also taking into account the underlying database properties when computing a cache validation key.
The desktop app contains a caching mechanism that automatically caches network requests on a per-URL and per-data-object status. However, the URL that's being used to communicate with the Docker containers is always the same (even if the underlying database is different). This means that some requests are wrongly being re-used. This PR fixes this by also taking into account the underlying database properties when computing a cache validation key.