-
Notifications
You must be signed in to change notification settings - Fork 422
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
Inconsistent results when extending parsed can.Models #1272
Milestone
Comments
It also looks like it is a regression. When I tested it, things worked in 2.1.3. |
Hi daffl- It might be important to note that all of these unexpected issues happen when findAll is defined in the parent models. This can be seen in the fiddle, but I didn't call it out in the original issue post. |
daffl
added a commit
that referenced
this issue
Nov 10, 2014
daffl
added a commit
that referenced
this issue
Nov 18, 2014
daffl
added a commit
that referenced
this issue
Nov 20, 2014
daffl
added a commit
that referenced
this issue
Nov 20, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've noticed the following issues when extending a can.Model:
This seems similiar to #1246
Fiddle here.
The text was updated successfully, but these errors were encountered: