Closed skbach closed 9 years ago
I'm guessing that this is a [docstring?] bug caused by https://github.com/ptaoussanis/faraday/commit/c8919eb60d1dc59b12db307fcbda2d32c0f3b1eb
Could you try again with {:expected :not-exists}
and let me know if that works? Thanks!
Ya, {:expected {:id :not-exists}} works as expected.
Is there somewhere I could've gleaned that from the docs/source myself? I'm not sure how the commit you mentioned broke that.
Thanks.
Hi,
This was introduced by me in: https://github.com/ptaoussanis/faraday/commit/c1ec999834b4218512b81e50d8645cec10e9f10c
Would have sworn i'd changed the doc string to match, but apparently not. Sorry about that.
Okay, closing this.
Thanks for the fix @mantree, much appreciated! For future commits, could I ask that you please always rebase on the latest master/dev branch to make sure you've got the latest code state? Was a minor doc-string clash in this case, but wouldn't want to risk you needlessly spending time on merge conflicts, etc.
Cheers! :-)
(far/create-table client-opts "test" [:id :s])
(far/query client-opts "test" {:id [:eq "x"]})
(far/put-item client-opts "test" {:id "x"} {:expected {:id false}})
I assumed the first time, the put should succeed, and the second time it should throw. The docs says to provide {:attr false} to ensure it doesn't already exist, but this results in it always failing, even the first time.
Thanks.