Skip to content
This repository has been archived by the owner on Mar 5, 2020. It is now read-only.

Use a model library #687

Closed
toolness opened this issue Apr 14, 2015 · 2 comments
Closed

Use a model library #687

toolness opened this issue Apr 14, 2015 · 2 comments

Comments

@toolness
Copy link
Contributor

We might want to consider using a "real" library for managing models and collections, e.g. Backbone.Model or ampersand-model, rather than doing things the ad-hoc way that we're currently doing.

Potential benefits:

  • Right now our ad-hoc mechanism updates the entire collection of Clubs wholesale; there isn't any way, for instance, to update only one Club or do pagination. Some model libraries could give us this functionality "for free". Maybe.
  • Our current mechanism doesn't trigger optimistic updates, which might be useful for responsiveness/latency compensation.
@toolness
Copy link
Contributor Author

Another option is to look into React's own Flux application architecture.

@toolness toolness self-assigned this Apr 23, 2015
@hannahkane hannahkane modified the milestone: May 8, 2015 Apr 23, 2015
@toolness
Copy link
Contributor Author

Update: the Flux application architecture doesn't really specify a particular way of storing models. And there's a new series of training videos on how to combine React with Ampersand.js and a number of other technologies.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants