Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: latest_backbone
Commits on May 13, 2012
  1. missing semicolon

    authored
Commits on May 12, 2012
  1. @saimonmoore
  2. @saimonmoore
Commits on Mar 30, 2012
  1. Huge refactor on proxy reset events. Only bubble to collections that …

    authored
    …will receive any add or remove
Commits on Feb 16, 2012
  1. malformed package.json

    authored
  2. added saimon as a contributor

    authored
  3. added saimon as a contributor

    authored
Commits on Feb 15, 2012
  1. @saimonmoore

    Bump version 0.0.3

    saimonmoore authored
    Added contributors
  2. @saimonmoore

    Add 'no_reset' option to NOT do a reset on construction but rather in…

    saimonmoore authored
    …itialize with existing parent models.
    
    i.e. it will ignore any models passed as args to the constructor and
    instead do an internal silent reset.
Commits on Feb 13, 2012
  1. Merge pull request #3 from masylum/dont_touch_parent

    authored
    When resetting parent (during a subset reset), don't remove the subset's models from the parent.
Commits on Feb 10, 2012
  1. @saimonmoore

    When resetting parent (during a subset reset), don't remove the subse…

    saimonmoore authored
    …t's models from the parent.
    
    The idea being that though these models may not belong to this
    particular subset any longer, they may still belong to another subset.
    The parent should always contain the superset of models.
    
    So when resetting the parent, we look for any models from the new set of
    models that are missing from the parent and include them.
    
    Additionally, when adding a model to a subset's own collection we try
    and look it up on the parent (so both collections reflect the same
    instance) and failing that we create a new model instance (if only
    attributes were added).
    
    Updated tests to reflect the multiple subset use case.
    
    Note: To avoid the parent's reset event from re-resetting the subset's
    collection, we mark the event with a 'subset_reset' option. We only act
    on proxied 'reset' events that don't have this marker. This has the
    additional benefit of not propagating the parent's (subset initiated) reset event to
    sibling subsets.
Commits on Feb 6, 2012
  1. lints, spaces and refactors

    authored
  2. propagate reset correctly

    authored
Commits on Feb 2, 2012
  1. @saimonmoore

    Clean out lint

    saimonmoore authored
  2. @saimonmoore

    Merge branch 'before_initialize'

    saimonmoore authored
    Conflicts:
    	test/test.js
  3. @saimonmoore
  4. @saimonmoore

    Fix backbone to 0.5.3

    saimonmoore authored
Commits on Jan 26, 2012
  1. @saimonmoore

    Merge pull request #1 from latentflip/liveupdating-subsets

    saimonmoore authored
    Liveupdating subsets
  2. @latentflip
Commits on Jan 25, 2012
  1. @latentflip
  2. @latentflip

    Add a liveupdate_keys option to keep the subset updated, when model a…

    latentflip authored
    …ttributes change that would make them now fail/pass the sieve.
    
    By default subset's will be liveupdated (liveupdate_keys = 'all').
    
    To limit the model keys on which the subset will be liveupdated, set liveupdate_keys to an array of model attributes. liveupdate_keys = ['archived', 'dated_on'].
Commits on Dec 1, 2011
  1. @saimonmoore
Commits on Nov 30, 2011
  1. @saimonmoore

    When resetting the subset, repopulate with filtered models from the p…

    saimonmoore authored
    …arent.
    
    All models in the subset should be the same instance as in the parent
    collection. Corrected test to reflect this.
Commits on Nov 25, 2011
  1. 0.0.2

    authored
  2. docs

    authored
  3. ignore node_modules

    authored
  4. first commit

    authored
Something went wrong with that request. Please try again.