Already deleted Message returns 404 vs 409 conflict when a 2nd attempt to delete is processed #739
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.
After merging #635, which was a bit old, one of the new tests failed upon merge to main.
During a
dwn-sdk-js
change the return for a conflictingRecordsDelete
changed from a409
to a404
.https://github.com/TBD54566975/dwn-sdk-js/pull/749/files#diff-169fe156eb9ea99859416850b92e6836907930a425399f2bcb059c9edf4259b6R57
This PR addresses it within the new
record.delete()
method, as well as for sync, adding additional coverage.