Log and asset changed filter is too restrictive

[paul121]

Describe the bug
Giving this a go with farmOS 3.x and all is working well, but in the process noticed one thing: no data was being returned with asset and log requests, but I know there are assets and logs in my test instance. After inspecting the API requests in the console I believe this is because the changed filter is simply too restrictive: instead of = I think this should be >, so we request all entities that were changed "after" the timestamp, not "at the" timestamp.

Request URL:

https://3.x.ddev.site/api/log/observation?filter[timestamp-0-filter][condition][path]=timestamp&filter[timestamp-0-filter][condition][operator]=>&filter[timestamp-0-filter][condition][value]=1696112413&filter[timestamp-1-filter][condition][path]=timestamp&filter[timestamp-1-filter][condition][operator]=<&filter[timestamp-1-filter][condition][value]=1700000413&filter[changed-0-filter][condition][path]=changed&filter[changed-0-filter][condition][operator]==&filter[changed-0-filter][condition][value]=1698704339

And console view of query params:

Copying this URL into my browser and changing the changed-0-filter operator to > returns data as expected.

I'm not entirely sure, but I think this is the relevant code in FK?

field-kit/packages/field-kit/src/idb/cache.js

Line 170 in 6365afd

if (settings.lastSync) filter.changed = settings.lastSync;

[jgaehring]

Thanks, Paul! Just glancing at this super fast, but I assume this is not related to farmOS/farmOS.js#86, correct?

I'm not entirely sure, but I think this is the relevant code in FK?

Ah, yea, could probably be remedied by changing it to:

if (settings.lastSync) filter.changed = { $gt: settings.lastSync };

Or $gte, just to be generous.

[paul121]

Correct, I do not think that this is related to farmOS/farmOS.js#86 - each of the filters here have unique IDs so that seems to be working well.

[jgaehring]

Once I wrap up the other remaining issues for the alpha.9 milestone, I'll see if this can be resolved easily enough, like I suggested it might above, and try to tack this on before tagging alpha.9. So I'm including this in the milestone for now. If it doesn't turn out to be as easy as all that, however, I may bump this back to the beta.1 release.