Store cache should not save client context
When a resource is saved in the cache, the client context used to expand properties is saved with it.
It causes some conflicts when another component uses the same resource with a different context, which is ignored by the store.
For example, we have a sib-display
loading a list of events. A sib-map
wants to display these events on a map, and for that, add this context:
{
"geo": "http://www.w3.org/2003/01/geo/wgs84_pos#",
"lat": "geo:lat",
"lng": "geo:long"
}
As the context already in the cache is preferred, no http://www.w3.org/2003/01/geo/wgs84_pos#lat
and http://www.w3.org/2003/01/geo/wgs84_pos#lng
are found in the resource, and nothing is displayed.
It probably need to re-think our store and cache architecture