foxnewsnetwork

import Ember from 'ember';

export default Ember.Component.extend({
  willInsertElement() {
    Ember.tryInvoke(this, 'action');
  }
}).reopenClass({
	positionalParams: ['action']
});

foxnewsnetwork

Motivation

Have you ever run into the infamous ember double render bug?

Do you find yourself breaking out import { scheduleOnce } from '@ember/runloop' all the time?

Are you frustrated about "god" components that can't be tested?

If so, this gist is for you!

foxnewsnetwork

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'QueryParams Demo',
  referrerLocation: null,
  queryParams: ['referrerLocation']
});

foxnewsnetwork

import Ember from 'ember';

export default Ember.Component.extend({
  tagName: '',
  
  after: 0,
  
  willDestroyElement() {
  	Ember.run.cancel(this.timeoutHandle);
  },

foxnewsnetwork

import Ember from 'ember';

export default Ember.Component.extend({
  tagName: 'canvas',
  
  attributeBindings: ['width', 'height'],
  
  width: 200,
  
  height: 274,

foxnewsnetwork

import Ember from 'ember';

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

foxnewsnetwork

import Ember from 'ember';

const DOGE = 'http://i0.kym-cdn.com/entries/icons/mobile/000/013/564/doge.jpg';
export default Ember.Controller.extend({
  appName: 'Ember Twiddle',
  DOGE
});

foxnewsnetwork

const COLLECTION = {
  "collection": {
    "id": "SOME-COLLECTION-ID",
    "name": "WALKING-SIMULATOR",
    "games": {
      "DEATH-STRANDING-XXX-1": {
        "id": "DEATH-STRANDING-XXX-1",
        "image": "https://i.ytimg.com/vi/i2nuHEGhwiw/sddefault.jpg"
        "genres": [
          { "id": "GENRE-ID-1" },

foxnewsnetwork

import Ember from 'ember';

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

foxnewsnetwork

Problem Background

Recently, I've been trying to experiment with using ReasonML in production, however, this generally involves writing bindings to existing libraries... and unfortunately, some of these libraries expose extremely difficult to type interfaces; consider trying to wrap the following getUserInfo function (written in typescript for illustration purposes):

type xInfo = {
    info: string,
    message: string
};