You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When posting a new edge, you can specify the serialization options to control the casing. However, in the methods used to patch an existing edge, there's no way to pass an options object used to serialize the edge data, and instead it's hard coded to use camel case. Is this the desired behaviour?
(There's also a bunch of different methods which seem to lack this parameter, and I can't seem to find a pattern on which method accepts it and which doesn't.)
We can provide a fix if this is something that should be changed.
The text was updated successfully, but these errors were encountered:
Nope. @tjoubert and I had a look, it seems to be an oversight. I've classified this as a bug.
Methods that serialize a document provided by the caller should expose serialization options. We should add an ApiClientSerializationOptions parameter to the following methods:
PatchVertexAsync
PatchEdgeAsync
PutVertexAsync
PutEdgeAsync
I think we should place it before the GraphHeaderProperties parameter, to be in line with PostVertexAsync and PostEdgeAsync.
We can provide a fix if this is something that should be changed.
That would be great! We welcome contributions. See also contribution guide.
JLedel
added a commit
to JLedel/arangodb-net-standard
that referenced
this issue
Oct 25, 2022
When posting a new edge, you can specify the serialization options to control the casing. However, in the methods used to patch an existing edge, there's no way to pass an options object used to serialize the edge data, and instead it's hard coded to use camel case. Is this the desired behaviour?
(There's also a bunch of different methods which seem to lack this parameter, and I can't seem to find a pattern on which method accepts it and which doesn't.)
We can provide a fix if this is something that should be changed.
The text was updated successfully, but these errors were encountered: