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.

Sign up for GitHub

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

Jump to bottom

Skipped tests for PATCH-to-replace (not present) #45

Closed
michielbdejong opened this issue Feb 14, 2021 · 1 comment
Closed

Skipped tests for PATCH-to-replace (not present) #45

michielbdejong opened this issue Feb 14, 2021 · 1 comment

Comments

@michielbdejong
Copy link
Collaborator

We don't know what the desired behaviour is for PATCH-to-replace (not present).

Since the issue of has not been settled yet at the spec level, we'll accept both behaviours for now.

See:

As soon as we know what the desired behaviour is, we'll test for that and can close this issue.
michielbdejong added a commit that referenced this issue Feb 14, 2021
@michielbdejong
Skip tests for PATCH-to-replace (not present)
6e50029 
#45
@michielbdejong michielbdejong mentioned this issue Mar 2, 2021
Closed
2 tasks
@michielbdejong michielbdejong changed the title [BLOCKED] Skipped tests for PATCH-to-replace (not present) Skipped tests for PATCH-to-replace (not present) Mar 5, 2021
@michielbdejong
Copy link
Collaborator Author

The test suite will start sending application/sparql-update-single-match as the Content-Type, and then we unskip this test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@michielbdejong