machty

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

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

  foo: task(function() {
    return {

machty

/* jshint node: true */

const EmberApp = require('ember-cli/lib/broccoli/ember-app');
const generateWhitelabelIndexes = require('./generate-whitelabel-indexes');

module.exports = function(defaults) {
  const app = new EmberApp(defaults, {
    // ...all sorts of config
  });

machty

import Ember from 'ember';

let guid = () => (Math.random().toString(36) + '00000000000000000').slice(2, 14)

export default Ember.Controller.extend({
  appName: 'Ember Twiddle',
  vol: Ember.computed(function() {
    return guid();
  }).volatile(),
  actions: {

machty

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

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

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

import Ember from 'ember';

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

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