Call parse before retrieving idAttribute

[kopatsy]

I have an API that returns the object payload as follow:
{
result : {
id : 123
field1 : ...
}
}

I have a custom parse method on my models that essentially does 'return response.result'.

In the findOrCreate method, the idAttribute must be retrieved and
it uses item[ type.prototype.idAttribute ]. This is fine when the
API returns the id as a top level key but it brakes otherwise and
parse must be called first.

I have not had a chance to write a unit test yet. I am new to javascript and backbone and I wanted to get your feedback on the change before I invest more time implementing a test case. This fix solves my particular problem but it may have side effects I am not aware of. Without this fix, I would get 'Cannot instantiate more than one Backbone.RelationalModel with the same id per type! ' errors since findOrCreate would never be able to pull the model idAttribute.

[DouweM]

Looks good to me. I can't think of any unwanted side effects, and for a change like this extra tests aren't necessary if you look at the level at which existing tests for this project are defined.

Thanks for your contribution!

PS. Sorry for the late response, I've been awfully busy lately.