Pier-Luc Gendreau
Pier-Luc Gendreau
Fair enough. The best I can offer you at the moment is to create defaults when said user signs up and then you don't have to worry about upserting.
It is not implemented, unfortunately. I remember looking at it some time back and there were some issues surrounding it but nothing insurmountable I would think.
Client-side upserts seem a bit odd, perhaps there is a specific use-case I'm missing?
Take a look at this answer from StackOverflow: http://stackoverflow.com/a/1269228/1779688
Bulk update and delete are very opinionated in the way resource identifiers should be passed and how errors should be handled. Bulk create is relatively simple, but I am reluctant...
TIL: I honestly was not aware of this method! Could you post a PR to run our tests?
By using `update`, we open the door to a bunch of useful methods, but it becomes rather complex to properly filter fields because we'd have to dig into a bunch...
I'm not too fond of adding deep endpoints, I think it should be left to the user to create routes that go beyond `/model/:id`, perhaps in the form of plugins....
Sounds right, thanks for the help @dwoodard !
It should work, are you getting an error?