Skip to content
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

Differentiate between models and collections #9

Open
uniqname opened this issue Nov 4, 2014 · 2 comments
Open

Differentiate between models and collections #9

uniqname opened this issue Nov 4, 2014 · 2 comments
Assignees

Comments

@uniqname
Copy link
Contributor

uniqname commented Nov 4, 2014

No description provided.

@designfrontier
Copy link
Member

To expand on the request... there needs to be a way to indicate that a model is a collection instead of a model (e.g. that it contains an array of objects and not specific attributes). This should include better URL handling in the ajaxMe section so that the individual models can be saved to the server without pushing the entire collection. Individual models should probably also respond to and send events around data.

@designfrontier
Copy link
Member

After more discussion collections should essentially be creators of models, creating models programmatically for each of the models that they contain.

@designfrontier designfrontier added this to the v0.7.0 Adam Baldwin milestone Nov 14, 2014
@designfrontier designfrontier self-assigned this Feb 24, 2015
designfrontier added a commit that referenced this issue Feb 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants