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
If you have an API that does not return the newly created object when you POST to the endpoint then angular-data craches because it tries to inject nothing into the datastore at the end of the create method. There should probably be an option or something to pass to create to make it not inject the result of the API call.
The text was updated successfully, but these errors were encountered:
That would make sense to me. Do you think it would make more sense for that option to be on the defineResource object or on a per operation basis (like the options passed to DS when you try to create)?
@kentcdodds probably makes more sense to have it pr operation, the same way this cacheResponse works. Since you might want to cache find to a resource but not create for instance. Or your would need multiple options on the defineResource object to handle setting these separately.
If you have an API that does not return the newly created object when you POST to the endpoint then angular-data craches because it tries to inject nothing into the datastore at the end of the create method. There should probably be an option or something to pass to create to make it not inject the result of the API call.
The text was updated successfully, but these errors were encountered: