grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Ember Twiddle'
});

grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Table Checkboxes'
});

grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Ember Twiddle',
  crazyNestedData: [{
    primaryData: "able-dataset_lvl-1",
    nestedData: [{
      primaryData: "able-dataset_lvl-2",
      nestedData: [{
        primaryData: "able-dataset_lvl-3",

grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Clock Service',
  clock: Ember.inject.service()
});

grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Loading Spinner Component'
});

grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Dropdown Component',
  
  menuSelectionOptions: [
  	Ember.Object.create({
      label: "Case#: 123",
      value: 1
    }),

grapho

import Ember from 'ember';

export default Ember.Controller.extend({

  appName:'Component Life-cycle Hooks',
  
  myAttr: "Red"

});

grapho

import Ember from 'ember';

export default Ember.Controller.extend({

  appName:'Component Life-cycle Hooks'
  
});

grapho

import Ember from 'ember';

export default Ember.Component.extend({
  /**
   Overall thoughts: Ember.Component needs a section in the module doc block outlining the order of events (just like the 1.13 blog post).
   Individual events can then refer back to that lifecycle chart to avoid the "runs xth during re-renders but only on thursdays" sentences.
   The module doc block should also get the section on what triggers a re-render (from the 1.13 blog post).
  */

  myProp: null,

grapho

import Ember from 'ember';

export default Ember.Controller.extend({
  appName:'Ember Twiddle',
  
  init() {
    this._super(...arguments);
    this.foos = [];
  },