biril
commented
10 years ago Hey, thanks for the input. I will have to look further into what you're proposing / want to do later on, but until then a couple clarifications:
"Make it so that you don't have to manually create fully-qualified models in the result handler. Instead, the result handler can return pure JSON and Backbone & Backbone.Relational will handle turning the result into Backbone Model instances."
I assume that in this context you're referring to route-handlers? If so, then what you're suggesting is how it currently works. Taken from the readme:
On success, the handler should return created Model attributes after handling a POST and updated Model attributes after handling a PUT or PATCH. Return Model attributes after handling a GET or an array of Model attributes after handling a GET that refers to a collection. Note that only attributes that have been changed on the server (and should be updated on the client) need to be included in returned hashes. Return nothing after handling a DELETE. On failure, the handler should return a string (presumably a custom error messsage, an HTTP status code that indicates failure, etc).
In the above, 'attributes' or 'hash' refer to plain objects which can be indeed represented as 'pure JSON'. Not models. It seems to me that this is basically what you want to be doing.
Regarding the undefined parse() that you mention, I'm guessing you're returning an array in response to a GET request for a model resource? If so, it's normal that this would produce an error as there's no defined way of converting an array into a model - and Backbone will try to do that. In absence of a custom parse() defined for exactly this purpose it will fail. You would get the same error returning an array from your server.
Let me know if this covers you or you want some other clarification or I'm missing your point, etc .. :)
nthsense
sonarcloud[bot]
... in the result handler. Instead, the result handler can return pure JSON and Backbone & Backbone.Relational will handle turning the result into Backbone Model instances. This also helps for cases where you're just using the Backbone Model to make the request and you're doing something unusual with the result in your model's success handler. Specifically, if the server returns an array in response to a GET call, we want faux-server to return that same array, and we want to do something with it in our success handler - but with faux-server calling resolve(result), we got a Backbone error that parse() was undefined.