oligriffiths

class Plugin
{
  shouldBuild() {
    return this.inputs.hasChanges();
  }
  
  build() {
    for (let input of this.inputs) {
      input.readFileSync('path/to/file');
    }

oligriffiths

The problem

Ember currently ships with ember data, and it is assumed that you will be using ember data within your application. The getting started guides also make the same assumption, and introduce ember data, before even mentioning that one can return a POJO or a promise that returns a POJO, for example an ajax request.

This contributes to the cognitive load of "learning ember" and I believe contributes substantially to the "steep learning curve" associated with learning ember. Ember data is indeed, a relatively complex product, with at least 4 core concepts to learn (models, store, adapters, serializers). To make matters worse, if your API isn't a nicely structure JSON-API, you're in for a hard time whilst you naviagte the ember data documentation to work out what to do. All of this is unnecessary to a new adopter to ember, and is likely to scare them off the framework entirely.

Background

Whilst some colleagues of mine worke

oligriffiths

Community Addons

liquid-fire

Comprehensive animation support for ambitious Ember applications

https://github.com/ember-animation/liquid-fire

ember-cli-flash

Simple, highly configurable flash messages for ember-cli.

oligriffiths

import Ember from 'ember';

import RSVP from 'rsvp';

//Make object proxy for promise
const ObjectPromiseProxy = Ember.ObjectProxy.extend(Ember.PromiseProxyMixin);

/**
* Returns a computed property that combines all dependent
* promises into an RSVP hash, which when resolves, calls

oligriffiths

# Remove remote references that have been deleted
git fetch -p

# Remove local branches that have been merged
git branch --merged | grep -v master | xargs git branch -d

oligriffiths

<?php
namespace Nooku\Component\Overrides;

use Nooku\Library;
use Nooku\Component\Users;

class UsersDispatcherAuthenticatorFacebook extends Library\DispatcherAuthenticatorAbstract
{
    /**
     * A redirect url

oligriffiths

<?php
/**
 * User: Oli Griffiths
 * Date: 06/03/15
 * Time: 09:53
 */

namespace Oligriffiths\Component\Foursquare;

use Nooku\Library;

oligriffiths

/**
 * Custom data adapter
 * 
 * Adapter delegates request methods to the entity resolver, rather than a regular ajax request.
 * Add/edit/delete methods are suppressed for this implementation but could easily be enabled
 * 
 ***/

module.exports = DS.Adapter.extend({

oligriffiths

<?php

/**

a. Embedding the user ID as a query string variable seems like a bad idea. I assume you’re using that to set a model state when you do your browse page. Here is what I would do:

1) create a settings controller if you haven’t already
2) depending upon which actions you need the user id set for, I would either set it as a model state in the controller constructor if you need user id set for all actions:

**/

oligriffiths

<?php
/**
 * @version     $Id$
 * @package     Nooku_Plugins
 * @subpackage  Koowa
 * @copyright   Copyright (C) 2007 - 2012 Johan Janssens. All rights reserved.
 * @license     GNU GPLv3 <http://www.gnu.org/licenses/gpl.html>
 * @link        http://www.nooku.org
 */