Ivan Yurov

If that's the case, why do we need option at all? But I'm not sure about that. As I recall, there was a difference... I have to run right now,...

So you were right, that internally the errors become the same json-api style, but what is generated by back-end is different: Here's what RESTAdapter expects: http://emberjs.com/api/data/classes/DS.RESTAdapter.html#toc_errors And JSONAPI expects the...

Yeah, I can do that, but it's again just a part of the story. You need to decide what to do with this whole errors handling thing. My understanding is...

Oh, and json-api declares format for batching the errors, like shown here: http://jsonapi.org/examples/#error-objects-multiple-errors I've never used it this way and not even sure, what could be the purpose, but shall...

Alright, let me prepare a PR for this

Actually, I think we could do something neater... I just quickly read that #215 issue and figured, why don't we leave response as something RAW that could be provided by...

The same for status code, usually it's just 422, so if we talk about field errors, that could be set automatically. Anyways, I'll think a bit about it and be...

Yeah, was buried by more urgent tasks. If open issue bothers you, let's close it for now and I'll return to it when I have a chance.

We just ran into an issue with `mockFindRecord` and `returns(model: ...)` after version update, so we'll be investigating after thanksgiving and address this thing too.

That issue is similar but subtly different, I suppose. I think it should be the other way around: validation (of particular field) should happen on focusout or submit, but errors...