Composite fields for a model ID


#1

I understand that the ID for an ember-data model object can be represented by a single field only. I’m working with an API where there there is no synthetic key - the keys are natural and in most cases composite.

Has anyone else in the community found themselves in this situation? If so, what approach did you take to solve the problem (assuming the constraint that you cannot change the backend API)? I’m guessing that I may need to write a custom adaptor (and more) to handle this. Any guidance would be appreciated.

Cheers.

-Joe


#2

Can you include an example of what the API response looks like?