machty

import Ember from 'ember';
import { subscription } from "../subscription";
import { bind } from '@ember/runloop';
import { task, timeout } from 'ember-concurrency';

export default Ember.Controller.extend({
  chatRooms:[ "EmberChat", "ReactChat", "VueChat", "AngularChat"],
  
  chatRoomName: null,
  

machty

import Ember from 'ember';

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

machty

import Ember from 'ember';

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

  foo: Ember.computed('bar', {
    set(key, value) {
      return `setter(${value})`;

machty

Ember Testing Journal

We've been driving all of our Ember tests with end-to-end Capybara tests running from our Rails server for some time. There are many upsides to this approach, but Capybara tests are generally slow and brittle, so we'd likely to start investing in client-side only Ember tests that don't actually hit the server at all.

Given that I don't have a lot of experience with Ember tests, I wanted to keep a journal of first impressions and snags I encountered along the way, so that perhaps this information will be useful for documentation maintainers or whomever.

Figuring out how to stub a service in an acceptance test

Screencast of me talking through my through process

machty

import { inject as service } from '@ember/service';
import Route from '@ember/routing/route';
const DEFAULT_INACTIVITY_TIMEOUT_MS = 10 * 60 * 1000

export default Route.extend({
  session: service(),
  userActivity: service(),
  notifications: service(),
  logoutTimeoutSubscription: null,
  activate() {

machty

Guide to loading/error events and substates

In addition to the techniques described in the Asynchronous Routing Guide, the Ember Router provides powerful yet overridable conventions for customizing asynchronous transitions between routes by making use of error and loading substates.

loading substates

machty

import Ember from 'ember';
import { task, timeout } from 'ember-concurrency';

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

  myTask: task(function * () {
    let didConfirm = yield this.get('getConfirmation').perform("Are you sure?");
    if (didConfirm) {
      alert("woot");

machty

import Ember from 'ember';

function * myGen() {
  yield 1;
  yield 2;
  yield 3;
}

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

machty

import Ember from 'ember';
import { task, timeout, waitForProperty } from 'ember-concurrency';

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

  foo: task(function * () {
    this.set('lol', 1);

machty

Loading Route Facelift

LoadingRoute has existed for a while, but it's barely useful and largely broken. It's never gotten much love due to it largely being a hangover of the router.js microlib, and we can make it better. The problems with LoadingRoute are intertwined with issues with facelift router's handling of async transitions in some cases, but of which need to be addressed, but here's a list of problems related to both:

• There's only one global LoadingRoute that gets activated when