PUT Annotation with added via field results in erronous HTTP 409 #66
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
bug
…efore comparing with new values Fixes #65
GGoetzelmann
force-pushed
the
issue-65-PUT_Annotation_with_added_via_field_results_in_erronous_HTTP_409
branch
from
7876c4d to
1c18d0d
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original issue description
Describe the bug
The user is unable to perform an update on an annotation that adds a via property.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The error likely stems from this claim in the WAP
https://www.w3.org/TR/annotation-protocol/#update-an-existing-annotation
However, this should never trigger if the via field does NOT pre-exist.
This bug likely also concerns the canonical property
closes #65