I can't speak for the "change what Ember expects" option, but I can say that this is precisely what blueprint overrides in Sails were invented for. This would be a perfectly reasonable way to make your app Ember-compatible.
Also keep in mind that all of the CRUD blueprints use the res.ok()
response to actually send data down to the client; if you like, you can just override that with your own api/responses/ok.js
, perhaps using req.url
to determine the resource that was being requested, and use that to wrap your JSON object in the manner that Ember expects.