-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
model.destroy() returning opts.success() with no DELETE xhr created #61
Comments
Looking at the source, this appears to happen if it thinks the model is new, i.e. if Can you log out |
Yeah that looks like the case. I was looking for this in the documentation, but it seems it was removed? Here's the link on ampersandjs.com under ampersand-model -> destroy: http://ampersandjs.com/docs#ampersand-model-isnew Here's the output:
After adding
So use Thanks for your help! |
mainIndex is for checking for existing copies of yourself in |
The model is removed from the collection when
category.destroy()
is invoked, yet no xhr request is made.Here's the console output,
![screen shot 2015-09-15 at 8 00 24 pm](https://cloud.githubusercontent.com/assets/7221494/9894831/b3b6ecb2-5be5-11e5-8e99-023c01535280.png)
res
is undefinedThe text was updated successfully, but these errors were encountered: