You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finally got some time to investigate a little more. Here is an issue I'm having using the version 1.0 branch.
I get this error when I try to find a user:
"Error: No model was found for 'id' at new Error (native) at Error.EmberError (http://0.0.0.0:4200/assets/vendor.js:25594:23) at Ember.Object.extend.modelFor (http://0.0.0.0:4200/assets/vendor.js:72988:19) at __exports__.default.JSONSerialize.extend.extractSingle (http://0.0.0.0:4200/assets/vendor.js:66134:28) at apply (http://0.0.0.0:4200/assets/vendor.js:30440:27) at superWrapper [as extractSingle] (http://0.0.0.0:4200/assets/vendor.js:30014:15) at __exports__.default.Ember.Object.extend.extractFind (http://0.0.0.0:4200/assets/vendor.js:65670:21) at __exports__.default.Ember.Object.extend.extract (http://0.0.0.0:4200/assets/vendor.js:65539:37) at http://0.0.0.0:4200/assets/vendor.js:73512:34 at tryCatch (http://0.0.0.0:4200/assets/vendor.js:57874:16)"
ED is using extractSingle method to handle this, because the response is
Hi,
Finally got some time to investigate a little more. Here is an issue I'm having using the version 1.0 branch.
I get this error when I try to find a user:
ED is using extractSingle method to handle this, because the response is
But, since it is expecting something like this:
it's assuming the first key is the model type to search for, but of course fails to find one.
Switching to ED beta 11 shows a different error (since it now actually tries with each key before failing), but problem persists.
I tried a solution and it worked for me, which was implementing extractSingle and modify the payload to what ED expects:
Overriding normalizedPayload won't work since we don't get passed the type, only the payload.
@dustinfarris @benkonrath do you see any problem with this approach?
The text was updated successfully, but these errors were encountered: