Joseph Chappell danielchappell

MaybeNot

Maybe you should use this instead of nullable types..

Installation

yarn add maybe-not

Everyday Use Example -- If this is crazytown skip to "In Practice aka Guides" section

Ember Core Concepts

The tutorial section of the Ember guides, starting with routes and templates

The entire Object Model section of the ember guides

An article I wrote on Computed Properties

Ember Guides Routing Section

Ember Training

A hands on guide to writting idomatic Ember.

##Contributions

This training guide and app was build and designed by Daniel Chappell and Kevin Boucher. Both this guide and the source code for the app are open source and completely free.

Please open an issue or submit a pull request for clairification or correction. Nothing is perfect with out help from the community, Thanks!

Computed Property Theory & Best Practices or Functional Programming in Ember or How I learned to stop worrying and love the Tomster.

In a nutshell, computed properties let you declare functions as properties. You create one by defining a computed property as a function, which Ember will automatically call when you ask for the property. You can then use it the same way you would any normal, static property. -- The Ember Guides

The Ember Object Model is the corner stone of Ember, and at the heart of the Object Model are computed properties.

The guides do a fine job giving need to know information on how to create and use computed properties and what to expect from the cacheing system they provide. However, I feel so much of the beauty that computed properties provide is lost in terse (but wonderful) documentation.

	import Ember from 'ember';

	export default Ember.Controller.extend({
	appName: 'Ember Twiddle',

	});

	import Ember from 'ember';

	// Ember 1.10

	export default Ember.Route.extend({

	//---fire in order on route enter---

	beforeModel(transition) {
	//empty by default