jimmy/postgrest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Removed test for RFC compliance

Browse Source 
Who would send Content-Range anyway, that is weird in this context
This commit is contained in:
Joe Nelson
2014-12-06 17:42:21 -08:00
parent f1ecbec543
commit 4eb4d8da1e
1 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/Feature/InsertSpec.hs
-7
View File
@@ -94,13 +94,6 @@ spec = around withApp $ do
context "with a fully-specified primary key" $ do context "with a fully-specified primary key" $ do
context "with Content-Range header" $
it "fails as per RFC7231" $
request methodPut "/compound_pk?k1=eq.1&k2=eq.2"
[("Content-Range", "0-0")]
[json| { "k1":1, "k2":2, "extra":3 } |]
`shouldRespondWith` 400
context "not specifying every column in the table" $ context "not specifying every column in the table" $
it "is rejected for lack of idempotence" $ it "is rejected for lack of idempotence" $
request methodPut "/compound_pk?k1=eq.12&k2=eq.42" [] request methodPut "/compound_pk?k1=eq.12&k2=eq.42" []