Socket
Socket
Sign inDemoInstall

ember-render-helpers

Package Overview
Dependencies
109
Maintainers
2
Versions
6
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    ember-render-helpers

Helpers that complement @ember/render-modifiers


Version published
Weekly downloads
7.7K
decreased by-17.44%
Maintainers
2
Created
Weekly downloads
 

Readme

Source

This project uses GitHub Actions for continuous integration.

ember-render-helpers

Use the {{did-insert}}, {{did-update}}, {{will-destroy}} modifiers from @ember/render-modifiers as template helpers.

The original idea came from this Pre-RFC.

Installation

ember install ember-render-helpers
Use Glint or <template> tag? ✨
  • Update your template registry to extend this addon's. Check the Glint documentation for more information.

    import '@glint/environment-ember-loose';
    
    import type EmberRenderHelpersRegistry from 'ember-render-helpers/template-registry';
    
    declare module '@glint/environment-ember-loose/registry' {
      export default interface Registry extends EmberRenderHelpersRegistry, /* other addon registries */ {
        // local entries
      }
    }
    
  • In a <template> tag, use the named import to consume the helpers.

    import { action } from '@ember/object';
    import Component from '@glimmer/component';
    import { didInsertHelper } from 'ember-render-helpers';
    
    export default class HelloComponent extends Component {
      @action sayHello() {
        console.log('Hello!');
      }
    
      <template>
        {{didInsertHelper this.sayHello}}
      </template>
    }
    

Usage

ember-render-helpers provides 3 helpers. To avoid name conflicts with @ember/render-modifiers, these helpers are suffixed with -helper.

  • {{did-insert-helper}}
  • {{did-update-helper}}
  • {{will-destroy-helper}}

All helpers expect a callback function as the 1st positional argument. You can pass parameters to this callback function as subsequent positional arguments, as named arguments, or using both.

{{did-insert-helper this.sayHello "Zoey"}}
import Component from '@glimmer/component';
import type { NamedParameters, PositionalParameters } from 'ember-render-helpers';

export default class HelloComponent extends Component {
  @action sayHello(positional: PositionalParameters, _named: NamedParameters) {
    const name = positional[0] as string;

    console.log(`Hello, ${name}!`);
  }
}

Example

Clicking the Toggle button will toggle the isVisible flag. When it switches to true, onDidInsert will be called, because the {{did-insert-helper}} helper is inserted. When it switches to false, onWillDestroy will be called, because the {{will-destroy-helper}} helper is removed.

Clicking the Random button will set randomValue to a new random value. Every time this happens, while isVisible is true, onDidUpdate will be called, because one of the parameters passed to the {{did-update-helper}} helper was updated.

Clicking the Random button does not cause {{did-insert-helper}} or {{will-destroy-helper}} to call onDidInsert and onWillDestroy, since these helpers are not triggered by parameter updates.

{{#if this.isVisible}}
  {{did-insert-helper   this.onDidInsert   1 2 3 this.randomValue foo="bar" qux="baz"}}
  {{will-destroy-helper this.onWillDestroy 1 2 3 this.randomValue foo="bar" qux="baz"}}
  {{did-update-helper   this.onDidUpdate   1 2 3 this.randomValue foo="bar" qux="baz"}}
{{/if}}

<button {{on "click" this.toggleVisibility}}>Toggle</button>
<button {{on "click" this.rollTheDice}}>Random</button>
import { action } from '@ember/object';
import Component from '@glimmer/component';
import { tracked } from '@glimmer/tracking';

export default class extends Component {
  @tracked isVisible = false;

  @tracked randomValue?: number;

  @action
  toggleVisibility() {
    this.isVisible = !this.isVisible;
  }

  @action
  rollTheDice() {
    this.randomValue = Math.random();
  }

  @action
  onDidInsert(positional: unknown[], named: Record<string, unknown>) {
    console.log({ positional, named });
    // => { positional: [1, 2, 3, 0.1337...], named: { foo: 'bar', qux: 'baz' } }
  }

  @action
  onWillDestroy(positional: unknown[], named: Record<string, unknown>) {
    console.log({ positional, named });
    // => { positional: [1, 2, 3, 0.1337...], named: { foo: 'bar', qux: 'baz' } }
  }

  @action
  onDidUpdate(positional: unknown[], named: Record<string, unknown>) {
    console.log({ positional, named });
    // => { positional: [1, 2, 3, 0.1337...], named: { foo: 'bar', qux: 'baz' } }
  }
}

Keywords

FAQs

Last updated on 30 Apr 2024

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc