Skip to content

Instantly share code, notes, and snippets.

tomdale / action.js
Created Oct 4, 2019
bind vs. action decorators
View action.js
import Component, { tracked, action } from '@glimmer/component';
export default class extends Component {
@tracked count = 0;
@action increment() {
tomdale / .vsls.json
Created Jul 11, 2019
Visual Studio Live Share gitignore configuration
View .vsls.json
"$schema": "",
tomdale / class-template.ts
Created Jun 4, 2019
Class Template Strawman
View class-template.ts
import Component, { gbs } from '@glimmer/component';
export default class extends Component {
static template = gbs`
<h1>Hello {{}}</h1>

Forwarding Named Blocks in Glimmer

Use Case

A component that "forwards" passed blocks to a child component. For example, imagine we have a component called MiniCard that accepts a named block called header. It is invoked like this:

    My Card
tomdale /
Last active Dec 22, 2018
Ember Component Lifecycle Hooks Survey

Component Lifecycle Hooks Survey

Most Ember developers are familiar with component lifecycle hooks, like didInsertElement, willDestroy, etc.

As we think about future APIs for Glimmer components that improve on lifecycle hooks, we want to make sure that we're providing abstractions that are simple, performant, and ergonomic, while nudging users towards good patterns and away from potential footguns.

tomdale / index.js
Created Dec 6, 2018
Tracked property notify API strawman
View index.js
import Timer from 'simple-timer';
import Component from '@glimmer/component';
import { } from '@glimmer/tracking';
export default class TimerComponent extends Component {
constructor() {
// Mark the timer as "untracked" (i.e., we're asserting
// that timer contains no interior tracked properties at all).
// This function gives us back the timer as well as a callback
// function to call when any interior mutation may have occurred.
View components.container-component.js
import Ember from 'ember';
export default Ember.Component.extend({
componentName: "inner-component",
actions: {
handleComponentChange() {
this.set('componentName', "second-component");
View bytecode-format.txt
/* Fixed Opcode */ /* Operand? */ /* Operand? */ /* Operand? */
I = instruction (opcode) type
L = operand length
R = reserved
A = operand value
View open-element.ts
APPEND_OPCODES.add(Op.OpenElement, (vm, { op1: tag }) => {
View program.js
const Program = [25, 1, 0, 0, 22, 2, 0, 0, 32, 0, 0, 0];
You can’t perform that action at this time.