Model::transaction provides a deep-copied, “shadow-realm” version of a record which is great for rendering into edit forms. Any changes made to it can be saved (which updates the original record too), or just forgotten.

Batman.js is a CoffeeScript front-end MVC framework. One of its core features is accessors, which can be used like properties or methods of a Batman.Object. They can even take arguments!

In this whirlwind tutorial, we’ll build a blog with batman.js and Firebase.

Implementing image preview is breeze thanks to batman.js observers and JavaScript APIs.

Batman.js doesn’t support hasManyThrough out of the box, but it can be implemented fairly easily with Set::mappedTo.

Batman.Object accessors are the bread and butter of batman.js. Stubbing them can make testing much easier.

batman.js views are one of the best ways to integrate other JS libraries with batman.js data structures like Batman.Object and Batman.Set. For example, you can use a custom view to display Batman.Models with leaflet.js

Batman.Set is the array-like enumerable of batman.js. It offers observable properties (which are automatically tracked by @accessor) and useful change events.

By default, Batman.Request sends data as HTTP form data. However, you can override this with Batman.RestStorage.

You can use jasmine to test batman.js controllers by looking them up from the controller directory, then executing actions with executeAction.