Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a CONFLICT error detail catered for mutations. #696

Merged
merged 1 commit into from Oct 15, 2021

Conversation

berngp
Copy link
Contributor

@berngp berngp commented Oct 15, 2021

Pull Request type

  • Bugfix
  • Feature
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Other (please describe):

Changes in this PR

Indicates the operation conflicts with the current state of the target resource.
Conflicts are most likely to occur in the context of a mutation.

For example, you may get a CONFLICT when writing a field with a reference value that is
older than the one already on the server, resulting in a version control conflict.

HTTP Mapping: 409 Conflict.
Error Type: FAILED_PRECONDITION

Indicates the operation conflicts with the current state of the target resource.
Conflicts are most likely to occur in the context of a mutation.

For example, you may get a CONFLICT when writing a field with a reference value that is
older than the one already on the server, resulting in a version control conflict.

HTTP Mapping: 409 Conflict.
Error Type: FAILED_PRECONDITION
@berngp berngp merged commit 8b1c011 into master Oct 15, 2021
@berngp berngp deleted the feature/error-conflict branch October 20, 2022 01:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants