arangodb-net-standard icon indicating copy to clipboard operation
arangodb-net-standard copied to clipboard

A consistent, comprehensive, minimal interface to enable .NET applications to use the complete range of features exposed by the ArangoDB REST API.

Results 53 arangodb-net-standard issues
Sort by recently updated
recently updated
newest added

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...

bug

Some XML doc tags `` had web links in them, which causes warnings. Web links should just be pasted as is. Some tags also used to reference a specific method...

`CursorResponse` doesn't follow the naming we use for all the responses. Renaming it to `PostCursorResponse` will be more consistent with how other responses are named. I find it is helpful...

enhancement
breaking change

Previously we rejected the idea of using an enum for the ArangoDB error codes, see: https://github.com/ArangoDB-Community/arangodb-net-standard/pull/15 However it would still be useful to include an enum in the repository that...

If you're using an active failover setup and happens to query a follower, or there is a leader change, you'll get an exception telling that the node is not a...

It looks like one of the HTTP API endpoint related to graphs is not implemented: `GET /_api/edges/{collection-id}`. https://www.arangodb.com/docs/stable/http/edge.html#read-in--or-outbound-edges I propose to create a new `GetEdges` method under `IGraphApiClient`/`GraphApiClient`. While all...

At the time of writing, the latest release is 2.0.1 but doesn't contain some of the items listed under section "Version 2.0" of the roadmap file. We should update the...

1. Added `ApiClientBase.GetResponseAsync()` to extract the response body and headers to an object of type `ApiResponse` where `T` is the response type. 2. Amended `ApiClientBase.GetApiErrorExceptionAsync()` to extract header values on...

enhancement
breaking change