Adolfo Builes abuiles

Ember.js Testing package was a great addition to the project. It allowed us to have fast specs to guarantee the defined behavior. However, there's no convention on how you should guarantee that your models, the heart of any Ember.js application, are valid in relation to your backend.

Put another way, if you have an User model with a name attribute, how can you be sure that your backend is still responding with {"user": {"name": "Your Name"}}? So, even though your acceptance specs pass, you're stubbing out your models with FIXTURES.

Most people either manually test their apps or create an end-to-end test with the backend server, which is slow as hell (think of Capybara). The good news is that there are conventions for solving this since like forever. One way to guarantee this integrity is via Contract tests (http://martinfowler.com/bliki/IntegrationContractTest.html). Basically, you have a test to guarantee your models are matching your backend.

Using server-side end-to-end tests have many drawbacks,

Cheat sheet extracted from https://www.youtube.com/watch?v=2zmUSoVMyRU by That JS Dude.

$()

If you pass any of the CSS selectors to $(<identifier>) you get the first element.

> $('a')

router.js Architecture

Let this serve as a guide for anyone who'd like to dig into router.js's internals, understand what's going on, and hopefully contribute!

Scope of router.js (et al)

router.js is most popularly known as the routing microlib used by the Ember.js Router, though other folk have been known to use it beyond Ember, including some Angular folk who weren't satisfied with

Ember Router Async Facelift

The Ember router is getting number of enhancements that will greatly enhance its power, reliability, predictability, and ability to handle asynchronous loading logic (so many abilities), particularly when used in conjunction with promises, though the API is friendly enough that a deep understanding of promises is not required for the simpler use cases.

	// Record changes to an ObjectProxy and allow them to be stepped through
	// or jumped to.
	//
	// For an example, see http://emberjs.jsbin.com/EJEcoxO/12/edit?html,js,output
	//
	// There is a bower/npm installable version of this library on GitHub:
	// https://github.com/mixonic/ember-vcr-proxy
	//

	(function (global) {

	App.Store = DS.Store.extend

	pushRecord: (type, record) ->
	key = type.underscore().pluralize()
	payload = {}
	payload[key] = [record]
	@pushPayload type, payload
	@getById type, record.id

	<!--Start button-->
	<table cellspacing="0" border="0" cellpadding="8" width="240">
	<tr>
	<td height="35" bgcolor="#33CC33" style="border-radius: 5px; -moz-border-radius: 5px; -webkit-border-radius: 5px; -khtml-border-radius: 5px; font-size: 16px; font-family: sans-serif; color: #333333; margin: 0; padding: 0; text-align: center;" class='vero-editable'>
	<a href="http://getvero.com" style="font-weight:bold; text-decoration:underline;color: #ffffff;text-decoration:none;">Check out your cart →</a>
	</td>
	</tr>
	</table>
	<!-- End button-->

	var empty, get, set,
	__hasProp = {}.hasOwnProperty;

	get = Ember.get;
	set = Ember.set;

	empty = function(obj) {
	var key;
	for (key in obj) {
	if (!__hasProp.call(obj, key)) continue;

	# Patch from https://github.com/rails/rails/pull/8862

	module ActionDispatch
	Request.class_eval do

	# Remove nils from the params hash
	def deep_munge(hash)
	hash.each do \|k, v\|
	case v
	when Array

	pojo = {awesome: false};
	Ember.defineProperty(pojo, 'computedAwesomeness', Ember.computed.not('awesome'));
	alert("Computed Awesomeness: " + Ember.get(pojo, 'computedAwesomeness'));