@simonc wrote:
Hello,
We’re having a hard time finding the best way to handle conflicting models from two APIs. Both APIs use JSONAPI and provide the
posts
andcomments
endpoints.Our Ember application needs to be able to use those two APIs on the same page. What would be the best approach?
We’ve tried creating a separate adapter for the second API but when the payload is parsed the records are stored in the first API’s posts
The application was developed using the first API api1.test.com/api/v1/posts and we now need to compare the posts from the second API api2.test.com/api/v2/posts.
Is there any way to completely encapsulate what comes from a specific API to avoid this kind of conflicts?
Thanks!
Posts: 1
Participants: 1