Conflict error should expose the name of a field that violates a unique constraint.

[wopol]

Currently, the package exposes the driver.IsConflict function, which allows us to check whether conflict occurs, but the only way to check which field caused that error is to parse the error message. It is not good and error-prone. Is it possible to add explicitly the conflicti_keys to the ArangoError struct? Or maybe you could propose another solution that allows clients to check field names.

[enikon]

Thank you for reporting the issue!
The helper function that extracts the key from the error message is now added:

meta, err := col.CreateDocument(ctx, docOverwrite)
overwriteMode := arangodb.CollectionDocumentCreateOverwriteModeConflict

// We try to add the same-key document the second time
metaConflict, err := col.CreateDocumentWithOptions(ctx, docOverwrite, arangodb.CollectionDocumentCreateOptions{
	OverwriteMode: overwriteMode.New(),
})
require.Error(t, err)
require.Equal(t, meta.Key, err.(shared.ArangoError).GetConflictKey())

When working with CreateDocuments, the errors for specific Document can be viewed using CollectionDocumentCreateResponseReader.Read.

Best regards.