ember-class-based-modifier


`

`js
// app/components/scroll-container.js

import Component from '@glimmer/component';
import { tracked } from '@glimmer/tracking';
import { action } from '@ember/object';

export default class ScrollContainerComponent extends Component {
@tracked scrollPosition = 0;

@action scrollToTop() {
this.scrollPosition = 0;
}
}
`

`handlebars
{{!-- app/templates/application.hbs --}}


A lot of content...

Back To Top

`

Example with Cleanup

If the functionality you add in the modifier needs to be torn down when the modifier is removed, you can use the willRemove hook.

For example, if you want to have your elements dance randomly on the page using setInterval, but you wanted to make sure that was canceled when the modifier was removed, you could do this:

`js
// app/modifiers/move-randomly.js

import { action } from '@ember/object';
import Modifier from 'ember-class-based-modifier';

const { random, round } = Math;
const DEFAULT_DELAY = 1000;

export default class MoveRandomlyModifier extends Modifier {
setIntervalId = null;

get delay() {
// get the named argument "delay" passed to the modifier
//
// {{move-randomly delay=@someNumber}}
// ~~~~~~~~~~~
//
return this.args.named.delay || DEFAULT_DELAY;
}

@action moveElement() {
let top = round(random() * 500);
let left = round(random() * 500);
this.element.style.transform = translate(${left}px, ${top}px);
}

didReceiveArguments() {
if (this.setIntervalId !== null) {
clearInterval(this.setIntervalId);
}

this.setIntervalId = setInterval(this.moveElement, this.delay);
}

willRemove() {
clearInterval(this.setIntervalId);
this.setIntervalId = null;
}
}
`

Usage:

`hbs



`

Example with Service Injection

You can also use services into your modifier, just like any other class in Ember.

For example, suppose you wanted to track click events with ember-metrics:

`js
// app/modifiers/track-click.js

import { action } from '@ember/object';
import { inject as service } from '@ember/service';
import Modifier from 'ember-class-based-modifier';

export default class TrackClickModifier extends Modifier {
@service metrics;

get eventName() {
// get the first positional argument passed to the modifier
//
// {{track-click "like-button-click" page="some page" title="some title"}}
// ~~~~~~~~~~~~~~~~~~~
//
return this.args.positional[0];
}

get options() {
// get the named arguments passed to the modifier
//
// {{track-click "like-button-click" page="some page" title="some title"}}
// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
//
return this.args.named;
}

@action onClick() {
this.metrics.trackEvent(this.eventName, this.options);
}

didInstall() {
this.element.addEventListener('click', this.onClick, true);
}

willRemove() {
this.element.removeEventListener('click', this.onClick, true);
}
}
`

Usage:

`hbs

Click Me!

`

Classic API

If you would like to use Ember.Object based APIs, such as this.get, this.set, this.setProperties, etc, you can import the "classic" base class instead, located at the import path ember-class-based-modifier/classic.

The examples above can be rewritten using the classic API:

`js
// app/modifiers/scroll-position.js

import { computed } from '@ember/object';
import Modifier from 'ember-class-based-modifier/classic';

export default Modifier.extend({
scrollPosition: computed('args.positional.[]', function() {
// get the first positional argument passed to the modifier
//
// {{scoll-position @someNumber relative=@someBoolean}}
// ~~~~~~~~~~~
//
return this.args.positional[0];
}),

isRelative: computed('args.named.relative', function() {
// get the named argument "relative" passed to the modifier
//
// {{scoll-position @someNumber relative=@someBoolean}}
// ~~~~~~~~~~~~
//
return this.args.named.relative;
}),

didReceiveArguments() {
if(this.isRelative) {
this.element.scrollTop += this.scrollPosition;
} else {
this.element.scrollTop = this.scrollPosition;
}
}
});
`

`js
// app/modifiers/move-randomly.js

import { action, computed } from '@ember/object';
import Modifier from 'ember-class-based-modifier/classic';

const { random, round } = Math;
const DEFAULT_DELAY = 1000;

export default Modifier.extend({
init() {
this._super(...arguments);
this.set('setIntervalId', null);
},

delay: computed('args.named.delay', function() {
// get the named argument "delay" passed to the modifier
//
// {{move-randomly delay=@someNumber}}
// ~~~~~~~~~~~
//
return this.args.named.delay || DEFAULT_DELAY;
}),

moveElement: action(function() {
let top = round(random() * 500);
let left = round(random() * 500);
this.element.style.transform = translate(${left}px, ${top}px);
}),

didReceiveArguments() {
let setIntervalId = this.get('setIntervalId');

if (setIntervalId !== null) {
clearInterval(setIntervalId);
}

setIntervalId = setInterval(this.moveElement, this.get('delay'));

this.set('setIntervalId', setIntervalId);
},

willRemove() {
clearInterval(this.setIntervalId);
this.setIntervalId = null;
}
});
`

`js
// app/modifiers/track-click.js

import { action, computed } from '@ember/object';
import { inject as service } from '@ember/service';
import Modifier from 'ember-class-based-modifier/classic';

export default Modifier.extend({
metrics: service(),

eventName: computed('args.positional.[]', function() {
// get the first positional argument passed to the modifier
//
// {{track-click "like-button-click" page="some page" title="some title"}}
// ~~~~~~~~~~~~~~~~~~~
//
return this.args.positional[0];
}),

options: computed('args.named', function() {
// get the named arguments passed to the modifier
//
// {{track-click "like-button-click" page="some page" title="some title"}}
// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
//
return this.args.named;
}),

onClick: action(function() {
this.metrics.trackEvent(this.get('eventName'), this.get('options'));
}),

didInstall() {
this.element.addEventListener('click', this.onClick, true);
}

willRemove() {
this.element.removeEventListener('click', this.onClick, true);
}
});
`

Whenever possible, it is recommended that you use the default "modern" API instead of the classic API.

TypeScript

Using the "modern" native class API, you can use .ts instead of .js and it'll just work, as long as you do runtime checks to narrow the types of your args when you access them.

`ts
// app/modifiers/scroll-position.ts
import Modifier from 'ember-class-based-modifier';

export default class ScrollPositionModifier extends Modifier {
// ...
}
`

But to avoid writing runtime checks, you can extend Modifier with your own args, similar to the way you would define your args for a Glimmer Component.

`ts
// app/modifiers/scroll-position.ts
import Modifier from 'ember-class-based-modifier';

interface ScrollPositionModifierArgs {
positional: [number],
named: {
relative: boolean
}
}

export default class ScrollPositionModifier extends Modifier {
get scrollPosition(): number {
// get the first positional argument passed to the modifier
//
// {{scoll-position @someNumber relative=@someBoolean}}
// ~~~~~~~~~~~
//
return this.args.positional[0];
}

get isRelative(): boolean {
// get the named argument "relative" passed to the modifier
//
// {{scoll-position @someNumber relative=@someBoolean}}
// ~~~~~~~~~~~~
//
return this.args.named.relative
}

didReceiveArguments() {
if(this.isRelative) {
this.element.scrollTop += this.scrollPosition;
} else {
this.element.scrollTop = this.scrollPosition;
}
}
}
`

See this pull request comment for a full discussion about using TypeScript with your Modifiers.

API

element

The DOM element the modifier is attached to.

args: { positional: Array, named: Object }

The arguments passed to the modifier. args.positional is an array of positional arguments, and args.named is an object containing the named arguments.

isDestroying

true if the modifier is in the process of being destroyed, or has already been destroyed.

isDestroyed

true if the modifier has already been destroyed.

constructor(owner, args) (or init() in classic API)

Constructor for the modifier. You must call super(...arguments) (or this._super(...arguments) in classic API) before performing other initialization. The element is not yet available at this point (i.e. its value is null during construction).

didReceiveArguments()

Called when the modifier is installed and anytime the arguments are updated.

didUpdateArguments()

Called anytime the arguments are updated but not on the initial install. Called before didReceiveArguments.

didInstall()

Called when the modifier is installed on the DOM element. Called after didReceiveArguments.

willRemove()

Called when the DOM element is about to be destroyed; use for removing event listeners on the element and other similar clean-up tasks.

willDestroy()

Called when the modifier itself is about to be destroyed; use for teardown code. Called after willRemove. The element is no longer available at this point (i.e. its value is null during teardown).

$3



































































	Install	Update	Remove	this.element	this.args
constructor()	(1)	❌	❌	❌	after super()
didUpdateArguments()	❌	(1)	❌	✔️	✔️
didReceiveArguments()	(2)	(2)	❌	✔️	✔️
didInstall()	(3)	❌	❌	✔️	✔️
willRemove()	❌	❌	(1)	✔️	✔️
willDestroy()	❌	❌	(2)	❌	✔️

* (#) Indicates the order of invocation for the lifecycle event.
* ❌ Indicates that the method is not invoked for a given lifecycle / property is not available.
* ✔️ Indicates that the property is available during the invocation of the given method.

API differences from ember-oo-modifiers

* Renamed package to ember-class-based-modifier.
* No Modifier.modifier() function.
* Classic API is located at ember-class-based-modifier/classic.
* Arguments, both positional and named, are available on this.args.
* Named arguments do not become properties on the modifier instance.
* Arguments are not passed to life-cycle hooks.
* Renamed didInsertElement to didInstall and willDestroyElement to willRemove. This is to emphasize that when the modifier is installed or removed, the underlying element may not be freshly inserted or about to go away. Therefore, it is important to perform clean-up work in the willRemove to reverse any modifications you made to the element.
* Changed life-cycle hook order: didReceiveArguments fires before didInstall, and didUpdateArguments fires before didReceiveArguments, mirroring the classic component life-cycle hooks ordering.
* Added willDestroy, isDestroying and isDestroyed` with the same semantics as Ember objects and Glimmer components.

Contributing
------------------------------------------------------------------------------

See the Contributing guide for details.

License
------------------------------------------------------------------------------

This project is licensed under the MIT License.