We had the task name included in deserialize errors. But the serializer should not care nor know what the name of the resource is.
Still, we want to have the name of the resource show up in the logs if a cache corruption happens. This should be added higher in the stack, consumers of the serializer API should catch the DeserializeError and wrap it in a contextual error that adds things the the resource name.
We had the task name included in deserialize errors. But the serializer should not care nor know what the name of the resource is.
Still, we want to have the name of the resource show up in the logs if a cache corruption happens. This should be added higher in the stack, consumers of the serializer API should catch the DeserializeError and wrap it in a contextual error that adds things the the resource name.