Cannot use existing update, delete queries as we require lastUpdated at field that is not in query
Query should have this in Clint side plugin..
This happens for datasync but it might be also for delta
CC @ssd71
Is this about being unable to update existing documents which do not have updatedAt?
This is about client side plugin that generates client side queries. Those queries do not have updatedat field that is required. As result entire client side generator is not working
Is this about being unable to update existing documents which do not have
updatedAt?
I guess we'll need a separate issue for this then?
@ssd71 This is probably fixed
@ssd71 This is probably fixed
@ssd71 is this issue fixed?
@ssd71 is this issue fixed?
@machi1990updatedAtfield will no longer be required by update mutations in datasync after #1771 , that is what this specific issue was about
But after conflicts are added, this issue will arise again with a different field (_version)
AFAIK we still don't generate sync queries(or anything for datasync) in client side generator plugin so maybe we should discuss if we should be doing that?
@ssd71 is this issue fixed?
@machi1990updatedAtfield will no longer be required by update mutations in datasync after #1771 , that is what this specific issue was aboutBut after conflicts are added, this issue will arise again with a different field (
_version)AFAIK we still don't generate sync queries(or anything for datasync) in client side generator plugin so maybe we should discuss if we should be doing that?
The issue mentions about the inability to use delete / update mutations, so I am wondering if https://github.com/aerogear/graphback/blob/master/packages/graphback-datasync/src/DataSyncPlugin.ts#L81 is not enough to make the conflict field generated.
Actually this issue will be resolved as
Adding just datasync will no longer require version on edits. We do not use graphback for client side queries in offix - we have our own generation.
Leaving for @ssd71 to close or ask questions