atomic-server
atomic-server copied to clipboard
Corrupt items - `Could not deserialize item` errors locally for Collections
I don't know why, but for some times now on my local machine, I got deserialization errors for external Resources. Every time, it's for a Collection on atomicdata.dev
. I think because these contain nested resources, but I'm not sure about this.
Fixing the issue
Let's try to replicate this. Perhaps by using the path
endpoint to fetch a collection using atomic-server
locally.
Dealing with corrupt resources
Previously, every time I had one corrupt resource, all were corrupt because of a migration. That's not the case here. So I think it makes sense to have a command to deal with corrupt resources. Maybe a fix-corrupt
command, which iterates over all resources, removes the ones who cannot be deserialized, and pastes the removes resources to the terminal.