Skip to content

Releases: VoliJS/NestedTypes

BackboneJS compatibility layer for Type-R

Choose a tag to compare

@gaperton gaperton released this 25 May 04:19

Consult with Type-R docs about new features. Most important one is aggregation tree and shared attributes.

https://volicon.github.io/Type-R/Getting_Started.html

WARNING: NestedTypes 1.3 code won't work without refactoring.

Bug fixes

Choose a tag to compare

@gaperton gaperton released this 24 Feb 23:07
  • fix of potential exception in collection's validation

1.3.0

Choose a tag to compare

@gaperton gaperton released this 17 Feb 00:29
  • Huge performance improvements.
  • Abstract models and collection support (will be documented soon, some info is here).
  • Declarative attribute-level validation.
  • Mixins like in React's createClass (will be documented, but it will just work as you expect).
  • First-class hierarchical stores (very cool, but here's the spearate manual needed, which is tbd).
  • Bug fixes
  • Core changes:
    • Version tokens for models and collections making possible precise and efficient cache invalidation.
      It makes possible things like React's "pure render" optimization and lazy evaluation with memoization like in new validation.
    • Events, REST, underscore support, and validation is refactored to mixins.
    • Removed unused backbone code. Now NestedTypes contains backbone's shim with View, Router and History for backward compatibility purposes.
    • NestedTypes passes modified backbone 1.2 test suite.
  • Experimental features (may be documented or removed later):
    • attribute proxies (has.proxy)
    • hardrefs (Model.take and Collection.take)

fixed .has.watcher

Choose a tag to compare

@gaperton gaperton released this 17 Nov 17:50
v1.2.2

Merge remote-tracking branch 'refs/remotes/origin/develop'

React integration support

Choose a tag to compare

@gaperton gaperton released this 13 Nov 02:41

Standalone build with React integration features

Choose a tag to compare

@gaperton gaperton released this 13 Nov 02:32

React integration is in nestedreact npm package.
https://github.com/Volicon/react-backbone.glue/

minor fixes

Choose a tag to compare

@gaperton gaperton released this 06 Nov 00:41
Merge remote-tracking branch 'refs/remotes/origin/develop'

Conflicts:
	package.json

Fixed Backbone.ajax override

Choose a tag to compare

@gaperton gaperton released this 05 Nov 20:38
1.1.7

proxied Backbone.ajax

Fixed Nested.$ and Nested.sync override

Choose a tag to compare

@gaperton gaperton released this 05 Nov 20:21
1.1.6

Merge remote-tracking branch 'refs/remotes/origin/develop'

Standalone build (backbone 1.1.2 linked in)

Choose a tag to compare

@gaperton gaperton released this 04 Nov 22:57
  • Fixed incompatibilities with backbone 1.2.x by removing backbone dependency, effective now and forever. Currently, stable backbone 1.1.2 is linked in.
  • npm package name is changed to just 'nestedtypes'. Thus, npm install nestedtypes.
  • Can be used as drop-in backbonejs replacement in your project.
  • Models has reference to the parent model through this._owner
  • When the same model is shared between tho other models, attempt to serialize the model which is not an owner will result in [Serialization Error] warning. In most of the cases, this warning is the sign of weird errors, because after loading data this shared models won't be shared any more.
  • Collections has new changes event, which can be used directly on collection instead of 'add remove change reset'. It's efficient, and fired only once during compound changes.
  • There are Collection.transaction( func ) method which can be used ad-hoc to group sequence of changes coming from inside of func to the single transaction, thus, firing just one 'changes' event. Helpful for reducing an amount of renders.
  • Every method declared on Collection can be turned to be transactional when its definition is wrapped in Nested.transaction.
  • Experimental features:
    • lazily evaluated hard references Model.take( ref ) and Collection.take( ref ). ref is the reference like in
    • attribute proxies for mixing in attributes, a : MyModel.proxy(). a members will be directly accessible in owner model.
  • There are completely new mechancs of Stores, which will be documented later, and will allow us to refactor collections with mutual references which has to be requested together (such as users-roles-channelSets). It will be documented later.