Repository navigation
Skipped tests for PATCH-to-replace (not present) #45
Description
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.
Activity
Skip tests for PATCH-to-replace (not present)
[-][BLOCKED] Skipped tests for PATCH-to-replace (not present)[/-][+]Skipped tests for PATCH-to-replace (not present)[/+]michielbdejong commentedon Mar 5, 2021
The test suite will start sending
application/sparql-update-single-matchas the Content-Type, and then we unskip this test.Fix solid-contrib#45