Still some of my users got `couldn't validate schema...` error :( I dove deeper into it and saw that sometimes collections don't have `lastModified` param which is required in the schema. What I suggest is to: - maybe not making it optional, but a) filter out records without it b) make it default to `new Date()` when function is called? - I think that every inconsistency in schema shouldn't throw a direct error, rather skip this entry and return all that matches, what do you think? It seems reasonable, as we can't predict how reMarkable will change their api. Also in this particular case only one entry isn't matching and the whole operation is rejected 😕 - last thing I want to mention is to maybe enable an option to hide user files from this error? It shouldn't expose direct files structure in just an error, don't you think? Thanks in advance!
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by Bartek532 and has received 10 comments.
Add a comment
Comment form would go here