Class Component
publicimport Component from '@ember/component';
A component is a reusable UI element that consists of a .hbs
template and an
optional JavaScript class that defines its behavior. For example, someone
might make a button
in the template and handle the click behavior in the
JavaScript file that shares the same name as the template.
Components are broken down into two categories:
- Components without JavaScript, that are based only on a template. These are called Template-only or TO components.
- Components with JavaScript, which consist of a template and a backing class.
Ember ships with two types of JavaScript classes for components:
- Glimmer components, imported from
@glimmer/component
, which are the default component's for Ember Octane (3.15) and more recent editions. - Classic components, imported from
@ember/component
, which were the default for older editions of Ember (pre 3.15).
Below is the documentation for Classic components. If you are looking for the API documentation for Template-only or Glimmer components, it is available here.
Defining a Classic Component
If you want to customize the component in order to handle events, transform
arguments or maintain internal state, you implement a subclass of Component
.
One example is to add computed properties to your component:
import Component from '@ember/component';
export default Component.extend({
displayName: computed('person.title', 'person.firstName', 'person.lastName', function() {
let { title, firstName, lastName } = this.person;
if (title) {
return `${title} ${lastName}`;
} else {
return `${firstName} ${lastName}`;
}
})
});
And then use it in the component's template:
<h1>{{this.displayName}}</h1>
{{yield}}
Customizing a Classic Component's HTML Element in JavaScript
HTML Tag
The default HTML tag name used for a component's HTML representation is div
.
This can be customized by setting the tagName
property.
Consider the following component class:
import Component from '@ember/component';
export default Component.extend({
tagName: 'em'
});
When invoked, this component would produce output that looks something like this:
<em id="ember1" class="ember-view"></em>
HTML class
Attribute
The HTML class
attribute of a component's tag can be set by providing a
classNames
property that is set to an array of strings:
import Component from '@ember/component';
export default Component.extend({
classNames: ['my-class', 'my-other-class']
});
Invoking this component will produce output that looks like this:
<div id="ember1" class="ember-view my-class my-other-class"></div>
class
attribute values can also be set by providing a classNameBindings
property set to an array of properties names for the component. The return
value of these properties will be added as part of the value for the
components's class
attribute. These properties can be computed properties:
import Component from '@ember/component';
import { computed } from '@ember/object';
export default Component.extend({
classNames: ['my-class', 'my-other-class'],
classNameBindings: ['propertyA', 'propertyB'],
propertyA: 'from-a',
propertyB: computed(function() {
if (someLogic) { return 'from-b'; }
})
});
Invoking this component will produce HTML that looks like:
<div id="ember1" class="ember-view my-class my-other-class from-a from-b"></div>
Note that classNames
and classNameBindings
is in addition to the class
attribute passed with the angle bracket invocation syntax. Therefore, if this
component was invoked like so:
<MyWidget class="from-invocation" />
The resulting HTML will look similar to this:
<div id="ember1" class="from-invocation ember-view my-class my-other-class from-a from-b"></div>
If the value of a class name binding returns a boolean the property name
itself will be used as the class name if the property is true. The class name
will not be added if the value is false
or undefined
.
import Component from '@ember/component';
export default Component.extend({
classNameBindings: ['hovered'],
hovered: true
});
Invoking this component will produce HTML that looks like:
<div id="ember1" class="ember-view hovered"></div>
Custom Class Names for Boolean Values
When using boolean class name bindings you can supply a string value other
than the property name for use as the class
HTML attribute by appending the
preferred value after a ":" character when defining the binding:
import Component from '@ember/component';
export default Component.extend({
classNameBindings: ['awesome:so-very-cool'],
awesome: true
});
Invoking this component will produce HTML that looks like:
<div id="ember1" class="ember-view so-very-cool"></div>
Boolean value class name bindings whose property names are in a camelCase-style format will be converted to a dasherized format:
import Component from '@ember/component';
export default Component.extend({
classNameBindings: ['isUrgent'],
isUrgent: true
});
Invoking this component will produce HTML that looks like:
<div id="ember1" class="ember-view is-urgent"></div>
Class name bindings can also refer to object values that are found by traversing a path relative to the component itself:
import Component from '@ember/component';
import EmberObject from '@ember/object';
export default Component.extend({
classNameBindings: ['messages.empty'],
messages: EmberObject.create({
empty: true
})
});
Invoking this component will produce HTML that looks like:
<div id="ember1" class="ember-view empty"></div>
If you want to add a class name for a property which evaluates to true and and a different class name if it evaluates to false, you can pass a binding like this:
import Component from '@ember/component';
export default Component.extend({
classNameBindings: ['isEnabled:enabled:disabled'],
isEnabled: true
});
Invoking this component will produce HTML that looks like:
<div id="ember1" class="ember-view enabled"></div>
When isEnabled is false
, the resulting HTML representation looks like this:
<div id="ember1" class="ember-view disabled"></div>
This syntax offers the convenience to add a class if a property is false
:
import Component from '@ember/component';
// Applies no class when isEnabled is true and class 'disabled' when isEnabled is false
export default Component.extend({
classNameBindings: ['isEnabled::disabled'],
isEnabled: true
});
Invoking this component when the isEnabled
property is true will produce
HTML that looks like:
<div id="ember1" class="ember-view"></div>
Invoking it when the isEnabled
property on the component is false
will
produce HTML that looks like:
<div id="ember1" class="ember-view disabled"></div>
Updates to the value of a class name binding will result in automatic update
of the HTML class
attribute in the component's rendered HTML
representation. If the value becomes false
or undefined
the class name
will be removed.
Both classNames
and classNameBindings
are concatenated properties. See
EmberObject documentation for more
information about concatenated properties.
Other HTML Attributes
The HTML attribute section of a component's tag can be set by providing an
attributeBindings
property set to an array of property names on the
component. The return value of these properties will be used as the value of
the component's HTML associated attribute:
import Component from '@ember/component';
export default Component.extend({
tagName: 'a',
attributeBindings: ['href'],
href: 'http://google.com'
});
Invoking this component will produce HTML that looks like:
<a id="ember1" class="ember-view" href="http://google.com"></a>
One property can be mapped on to another by placing a ":" between the source property and the destination property:
import Component from '@ember/component';
export default Component.extend({
tagName: 'a',
attributeBindings: ['url:href'],
url: 'http://google.com'
});
Invoking this component will produce HTML that looks like:
<a id="ember1" class="ember-view" href="http://google.com"></a>
HTML attributes passed with angle bracket invocations will take precedence
over those specified in attributeBindings
. Therefore, if this component was
invoked like so:
<MyAnchor href="http://bing.com" @url="http://google.com" />
The resulting HTML will looks like this:
<a id="ember1" class="ember-view" href="http://bing.com"></a>
Note that the href
attribute is ultimately set to http://bing.com
, despite
it having attribute binidng to the url
property, which was set to
http://google.com
.
Namespaced attributes (e.g. xlink:href
) are supported, but have to be
mapped, since :
is not a valid character for properties in Javascript:
import Component from '@ember/component';
export default Component.extend({
tagName: 'use',
attributeBindings: ['xlinkHref:xlink:href'],
xlinkHref: '#triangle'
});
Invoking this component will produce HTML that looks like:
<use xlink:href="#triangle"></use>
If the value of a property monitored by attributeBindings
is a boolean, the
attribute will be present or absent depending on the value:
import Component from '@ember/component';
export default Component.extend({
tagName: 'input',
attributeBindings: ['disabled'],
disabled: false
});
Invoking this component will produce HTML that looks like:
<input id="ember1" class="ember-view" />
attributeBindings
can refer to computed properties:
import Component from '@ember/component';
import { computed } from '@ember/object';
export default Component.extend({
tagName: 'input',
attributeBindings: ['disabled'],
disabled: computed(function() {
if (someLogic) {
return true;
} else {
return false;
}
})
});
To prevent setting an attribute altogether, use null
or undefined
as the
value of the property used in attributeBindings
:
import Component from '@ember/component';
export default Component.extend({
tagName: 'form',
attributeBindings: ['novalidate'],
novalidate: null
});
Updates to the property of an attribute binding will result in automatic update of the HTML attribute in the component's HTML output.
attributeBindings
is a concatenated property. See
EmberObject documentation for more
information about concatenated properties.
Layouts
The layout
property can be used to dynamically specify a template associated
with a component class, instead of relying on Ember to link together a
component class and a template based on file names.
In general, applications should not use this feature, but it's commonly used in addons for historical reasons.
The layout
property should be set to the default export of a template
module, which is the name of a template file without the .hbs
extension.
<h1>Person's Title</h1>
<div class='details'>{{yield}}</div>
import Component from '@ember/component';
import layout from '../templates/components/person-profile';
export default Component.extend({
layout
});
If you invoke the component:
<PersonProfile>
<h2>Chief Basket Weaver</h2>
<h3>Fisherman Industries</h3>
</PersonProfile>
or
{{#person-profile}}
<h2>Chief Basket Weaver</h2>
<h3>Fisherman Industries</h3>
{{/person-profile}}
It will result in the following HTML output:
<h1>Person's Title</h1>
<div class="details">
<h2>Chief Basket Weaver</h2>
<h3>Fisherman Industries</h3>
</div>
Handling Browser Events
There are two ways to handle user-initiated events:
Using the on
modifier to capture browser events
In a component's template, you can attach an event handler to any element with the on
modifier:
<button {{on 'click' this.doSomething}} />
This will call the function on your component:
import Component from '@ember/component';
export default class ExampleComponent extends Component {
doSomething = (event) => {
// `event` is the native click Event
console.log('clicked on the button');
};
});
See the Guide on Component event
handlers
and the API docs for on
for more details.
Event Handler Methods
Components can also respond to user-initiated events by implementing a method that matches the event name. This approach is appropriate when the same event should be handled by all instances of the same component.
An event object will be passed as the argument to the event handler method.
import Component from '@ember/component';
export default Component.extend({
click(event) {
// `event.target` is either the component's element or one of its children
let tag = event.target.tagName.toLowerCase();
console.log('clicked on a `<${tag}>` HTML element!');
}
});
In this example, whenever the user clicked anywhere inside the component, it will log a message to the console.
It is possible to handle event types other than click
by implementing the
following event handler methods. In addition, custom events can be registered
by using Application.customEvents
.
Touch events:
touchStart
touchMove
touchEnd
touchCancel
Keyboard events:
keyDown
keyUp
keyPress
Mouse events:
mouseDown
mouseUp
contextMenu
click
doubleClick
focusIn
focusOut
Form events:
submit
change
focusIn
focusOut
input
Drag and drop events:
dragStart
drag
dragEnter
dragLeave
dragOver
dragEnd
drop
addObserver (key, target, method, sync) Observable public
Inherited from Observable packages/@ember/object/observable.ts:251
- key
- String
The key to observe
- target
- Object
The target object to invoke
- method
- String|Function
The method to invoke
- sync
- Boolean
Whether the observer is sync or not
- returns
- Observable
Adds an observer on a property.
This is the core method used to register an observer for a property.
Once you call this method, any time the key's value is set, your observer will be notified. Note that the observers are triggered any time the value is set, regardless of whether it has actually changed. Your observer should be prepared to handle that.
There are two common invocation patterns for .addObserver()
:
- Passing two arguments:
- the name of the property to observe (as a string)
- the function to invoke (an actual function)
- Passing three arguments:
- the name of the property to observe (as a string)
- the target object (will be used to look up and invoke a function on)
- the name of the function to invoke on the target object (as a string).
import Component from '@ember/component';
export default Component.extend({
init() {
this._super(...arguments);
// the following are equivalent:
// using three arguments
this.addObserver('foo', this, 'fooDidChange');
// using two arguments
this.addObserver('foo', (...args) => {
this.fooDidChange(...args);
});
},
fooDidChange() {
// your custom logic code
}
});
Observer Methods
Observer methods have the following signature:
import Component from '@ember/component';
export default Component.extend({
init() {
this._super(...arguments);
this.addObserver('foo', this, 'fooDidChange');
},
fooDidChange(sender, key, value, rev) {
// your code
}
});
The sender
is the object that changed. The key
is the property that
changes. The value
property is currently reserved and unused. The rev
is the last property revision of the object when it changed, which you can
use to detect if the key value has really changed or not.
Usually you will not need the value or revision parameters at the end. In this case, it is common to write observer methods that take only a sender and key value as parameters or, if you aren't interested in any of these values, to write an observer that has no parameters at all.
cacheFor (keyName) Object public
Inherited from Observable packages/@ember/object/observable.ts:407
- keyName
- String
- returns
- Object
The cached value of the computed property, if any
Returns the cached value of a computed property, if it exists. This allows you to inspect the value of a computed property without accidentally invoking it if it is intended to be generated lazily.
decrementProperty (keyName, decrement) Number public
Inherited from Observable packages/@ember/object/observable.ts:375
- keyName
- String
The name of the property to decrement
- decrement
- Number
The amount to decrement by. Defaults to 1
- returns
- Number
The new property value
Set the value of a property to the current value minus some amount.
player.decrementProperty('lives');
orc.decrementProperty('health', 5);
destroy EmberObject public
Inherited from CoreObject packages/@ember/object/core.ts:540
- returns
- EmberObject
receiver
Destroys an object by setting the isDestroyed
flag and removing its
metadata, which effectively destroys observers and bindings.
If you try to set a property on a destroyed object, an exception will be raised.
Note that destruction is scheduled for the end of the run loop and does not happen immediately. It will set an isDestroying flag immediately.
didReceiveAttrs public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:42
Available since v1.13.0
Called when the attributes passed into the component have been updated. Called both during the initial render of a container and during a rerender. Can be used in place of an observer; code placed here will be executed every time any attribute updates.
didRender public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:63
Available since v1.13.0
Called after a component has been rendered, both on initial render and in subsequent rerenders.
didUpdate public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:131
Available since v1.13.0
Called when the component has updated and rerendered itself. Called only during a rerender, not during an initial render.
didUpdateAttrs public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:97
Available since v1.13.0
Called when the attributes passed into the component have been changed. Called only during a rerender, not during an initial render.
get (keyName) Object public
Inherited from Observable packages/@ember/object/observable.ts:97
- keyName
- String
The property to retrieve
- returns
- Object
The property value or undefined.
Retrieves the value of a property from the object.
This method is usually similar to using object[keyName]
or object.keyName
,
however it supports both computed properties and the unknownProperty
handler.
Because get
unifies the syntax for accessing all these kinds
of properties, it can make many refactorings easier, such as replacing a
simple property with a computed property, or vice versa.
Computed Properties
Computed properties are methods defined with the property
modifier
declared at the end, such as:
import { computed } from '@ember/object';
fullName: computed('firstName', 'lastName', function() {
return this.get('firstName') + ' ' + this.get('lastName');
})
When you call get
on a computed property, the function will be
called and the return value will be returned instead of the function
itself.
Unknown Properties
Likewise, if you try to call get
on a property whose value is
undefined
, the unknownProperty()
method will be called on the object.
If this method returns any value other than undefined
, it will be returned
instead. This allows you to implement "virtual" properties that are
not defined upfront.
getProperties (list) Object public
Inherited from Observable packages/@ember/object/observable.ts:141
- list
- String...|Array
of keys to get
- returns
- Object
To get the values of multiple properties at once, call getProperties
with a list of strings or an array:
record.getProperties('firstName', 'lastName', 'zipCode');
// { firstName: 'John', lastName: 'Doe', zipCode: '10011' }
is equivalent to:
record.getProperties(['firstName', 'lastName', 'zipCode']);
// { firstName: 'John', lastName: 'Doe', zipCode: '10011' }
has (name) Boolean public
Inherited from Evented packages/@ember/object/evented.ts:137
- name
- String
The name of the event
- returns
- Boolean
does the object have a subscription for event
Checks to see if object has any subscriptions for named event.
incrementProperty (keyName, increment) Number public
Inherited from Observable packages/@ember/object/observable.ts:358
- keyName
- String
The name of the property to increment
- increment
- Number
The amount to increment by. Defaults to 1
- returns
- Number
The new property value
Set the value of a property to the current value plus some amount.
person.incrementProperty('age');
team.incrementProperty('score', 2);
init public
Inherited from CoreObject packages/@ember/object/core.ts:321
An overridable method called when objects are instantiated. By default, does nothing unless it is overridden during class definition.
Example:
import EmberObject from '@ember/object';
const Person = EmberObject.extend({
init() {
alert(`Name is ${this.get('name')}`);
}
});
let steve = Person.create({
name: 'Steve'
});
// alerts 'Name is Steve'.
NOTE: If you do override init
for a framework class like Component
from @ember/component
, be sure to call this._super(...arguments)
in your init
declaration!
If you don't, Ember may not have an opportunity to
do important setup work, and you'll see strange behavior in your
application.
notifyPropertyChange (keyName) Observable public
Inherited from Observable packages/@ember/object/observable.ts:233
- keyName
- String
The property key to be notified about.
- returns
- Observable
Convenience method to call propertyWillChange
and propertyDidChange
in
succession.
Notify the observer system that a property has just changed.
Sometimes you need to change a value directly or indirectly without
actually calling get()
or set()
on it. In this case, you can use this
method instead. Calling this method will notify all observers that the
property has potentially changed value.
off (name, target, method) public
Inherited from Evented packages/@ember/object/evented.ts:121
- name
- String
The name of the event
- target
- Object
The target of the subscription
- method
- Function|String
The function or the name of a function of the subscription
- returns
this
Cancels subscription for given name, target, and method.
on (name, target, method) public
Inherited from Evented packages/@ember/object/evented.ts:51
- name
- String
The name of the event
- target
- Object
The "this" binding for the callback
- method
- Function|String
A function or the name of a function to be called on
target
- returns
this
Subscribes to a named event with given function.
person.on('didLoad', function() {
// fired once the person has loaded
});
An optional target can be passed in as the 2nd argument that will be set as the "this" for the callback. This is a good way to give your function access to the object triggering the event. When the target parameter is used the callback method becomes the third argument.
one (name, target, method) public
Inherited from Evented packages/@ember/object/evented.ts:78
- name
- String
The name of the event
- target
- Object
The "this" binding for the callback
- method
- Function|String
A function or the name of a function to be called on
target
- returns
this
Subscribes a function to a named event and then cancels the subscription
after the first time the event is triggered. It is good to use one
when
you only care about the first time an event has taken place.
This function takes an optional 2nd argument that will become the "this" value for the callback. When the target parameter is used the callback method becomes the third argument.
readDOMAttr (name) public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:931
- name
- String
the name of the attribute
- returns
String
Normally, Ember's component model is "write-only". The component takes a bunch of attributes that it got passed in, and uses them to render its template.
One nice thing about this model is that if you try to set a value to the same thing as last time, Ember (through HTMLBars) will avoid doing any work on the DOM.
This is not just a performance optimization. If an attribute has not
changed, it is important not to clobber the element's "hidden state".
For example, if you set an input's value
to the same value as before,
it will clobber selection state and cursor position. In other words,
setting an attribute is not always idempotent.
This method provides a way to read an element's attribute and also update the last value Ember knows about at the same time. This makes setting an attribute idempotent.
In particular, what this means is that if you get an <input>
element's
value
attribute and then re-render the template with the same value,
it will avoid clobbering the cursor and selection position.
Since most attribute sets are idempotent in the browser, you typically
can get away with reading attributes using jQuery, but the most reliable
way to do so is through this method.
removeObserver (key, target, method, sync) Observable public
Inherited from Observable packages/@ember/object/observable.ts:337
- key
- String
The key to observe
- target
- Object
The target object to invoke
- method
- String|Function
The method to invoke
- sync
- Boolean
Whether the observer is async or not
- returns
- Observable
Remove an observer you have previously registered on this object. Pass
the same key, target, and method you passed to addObserver()
and your
target will no longer receive notifications.
rerender public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:141
Renders the view again. This will work regardless of whether the view is already in the DOM or not. If the view is in the DOM, the rendering process will be deferred to give bindings a chance to synchronize.
If children were added during the rendering process using appendChild
,
rerender
will remove them, because they will be added again
if needed by the next render
.
In general, if the display of your view changes, you should modify
the DOM element directly instead of manually calling rerender
, which can
be slow.
send (actionName, context) public
Inherited from Ember.ActionHandler packages/@ember/-internals/runtime/lib/mixins/action_handler.ts:172
- actionName
- String
The action to trigger
- context
- *
a context to send with the action
Triggers a named action on the ActionHandler
. Any parameters
supplied after the actionName
string will be passed as arguments
to the action target function.
If the ActionHandler
has its target
property set, actions may
bubble to the target
. Bubbling happens when an actionName
can
not be found in the ActionHandler
's actions
hash or if the
action target function returns true
.
Example
import Route from '@ember/routing/route';
export default Route.extend({
actions: {
playTheme() {
this.send('playMusic', 'theme.mp3');
},
playMusic(track) {
// ...
}
}
});
set (keyName, value) Object public
Inherited from Observable packages/@ember/object/observable.ts:168
- keyName
- String
The property to set
- value
- Object
The value to set or
null
.- returns
- Object
The passed value
Sets the provided key or path to the value.
record.set("key", value);
This method is generally very similar to calling object["key"] = value
or
object.key = value
, except that it provides support for computed
properties, the setUnknownProperty()
method and property observers.
Computed Properties
If you try to set a value on a key that has a computed property handler
defined (see the get()
method for an example), then set()
will call
that method, passing both the value and key instead of simply changing
the value itself. This is useful for those times when you need to
implement a property that is composed of one or more member
properties.
Unknown Properties
If you try to set a value on a key that is undefined in the target
object, then the setUnknownProperty()
handler will be called instead. This
gives you an opportunity to implement complex "virtual" properties that
are not predefined on the object. If setUnknownProperty()
returns
undefined, then set()
will simply set the value on the object.
Property Observers
In addition to changing the property, set()
will also register a property
change with the object. Unless you have placed this call inside of a
beginPropertyChanges()
and endPropertyChanges(),
any "local" observers
(i.e. observer methods declared on the same object), will be called
immediately. Any "remote" observers (i.e. observer methods declared on
another object) will be placed in a queue and called at a later time in a
coalesced manner.
setProperties (hash) Object public
Inherited from Observable packages/@ember/object/observable.ts:216
- hash
- Object
the hash of keys and values to set
- returns
- Object
The passed in hash
Sets a list of properties at once. These properties are set inside
a single beginPropertyChanges
and endPropertyChanges
batch, so
observers will be buffered.
record.setProperties({ firstName: 'Charles', lastName: 'Jolley' });
toString String public
Inherited from CoreObject packages/@ember/object/core.ts:575
- returns
- String
string representation
Returns a string representation which attempts to provide more information
than Javascript's toString
typically does, in a generic way for all Ember
objects.
import EmberObject from '@ember/object';
const Person = EmberObject.extend();
person = Person.create();
person.toString(); //=> "<Person:ember1024>"
If the object's class is not defined on an Ember namespace, it will indicate it is a subclass of the registered superclass:
const Student = Person.extend();
let student = Student.create();
student.toString(); //=> "<(subclass of Person):ember1025>"
If the method toStringExtension
is defined, its return value will be
included in the output.
const Teacher = Person.extend({
toStringExtension() {
return this.get('fullName');
}
});
teacher = Teacher.create();
teacher.toString(); //=> "<Teacher:ember1026:Tom Dale>"
toggleProperty (keyName) Boolean public
Inherited from Observable packages/@ember/object/observable.ts:392
- keyName
- String
The name of the property to toggle
- returns
- Boolean
The new property value
Set the value of a boolean property to the opposite of its current value.
starship.toggleProperty('warpDriveEngaged');
trigger (name, args) public
Inherited from Evented packages/@ember/object/evented.ts:100
- name
- String
The name of the event
- args
- Object...
Optional arguments to pass on
Triggers a named event for the object. Any additional arguments will be passed as parameters to the functions that are subscribed to the event.
person.on('didEat', function(food) {
console.log('person ate some ' + food);
});
person.trigger('didEat', 'broccoli');
// outputs: person ate some broccoli
willDestroy public
Inherited from CoreObject packages/@ember/object/core.ts:567
Override to implement teardown.
willRender public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:80
Available since v1.13.0
Called before a component has been rendered, both on initial render and in subsequent rerenders.
willUpdate public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:114
Available since v1.13.0
Called when the component is about to update and rerender itself. Called only during a rerender, not during an initial render.
actions public
Inherited from Ember.ActionHandler packages/@ember/-internals/runtime/lib/mixins/action_handler.ts:27
The collection of functions, keyed by name, available on this
ActionHandler
as action targets.
These functions will be invoked when a matching {{action}}
is triggered
from within a template and the application's current route is this route.
Actions can also be invoked from other parts of your application
via ActionHandler#send
.
The actions
hash will inherit action handlers from
the actions
hash defined on extended parent classes
or mixins rather than just replace the entire hash, e.g.:
import Mixin from '@ember/object/mixin';
export default Mixin.create({
actions: {
displayBanner(msg) {
// ...
}
}
});
import Route from '@ember/routing/route';
import CanDisplayBanner from '../mixins/can-display-banner';
export default Route.extend(CanDisplayBanner, {
actions: {
playMusic() {
// ...
}
}
});
// `WelcomeRoute`, when active, will be able to respond
// to both actions, since the actions hash is merged rather
// then replaced when extending mixins / parent classes.
this.send('displayBanner');
this.send('playMusic');
Within a Controller, Route or Component's action handler,
the value of the this
context is the Controller, Route or
Component object:
import Route from '@ember/routing/route';
export default Route.extend({
actions: {
myAction() {
this.controllerFor("song");
this.transitionTo("other.route");
...
}
}
});
It is also possible to call this._super(...arguments)
from within an
action handler if it overrides a handler defined on a parent
class or mixin:
Take for example the following routes:
import Mixin from '@ember/object/mixin';
export default Mixin.create({
actions: {
debugRouteInformation() {
console.debug("It's a-me, console.debug!");
}
}
});
import Route from '@ember/routing/route';
import DebugRoute from '../mixins/debug-route';
export default Route.extend(DebugRoute, {
actions: {
debugRouteInformation() {
// also call the debugRouteInformation of mixed in DebugRoute
this._super(...arguments);
// show additional annoyance
window.alert(...);
}
}
});
Bubbling
By default, an action will stop bubbling once a handler defined
on the actions
hash handles it. To continue bubbling the action,
you must return true
from the handler:
Router.map(function() {
this.route("album", function() {
this.route("song");
});
});
import Route from '@ember/routing/route';
export default Route.extend({
actions: {
startPlaying: function() {
}
}
});
import Route from '@ember/routing/route';
export default Route.extend({
actions: {
startPlaying() {
// ...
if (actionShouldAlsoBeTriggeredOnParentRoute) {
return true;
}
}
}
});
ariaRole public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:1131
The WAI-ARIA role of the control represented by this view. For example, a button may have a role of type 'button', or a pane may have a role of type 'alertdialog'. This property is used by assistive software to help visually challenged users navigate rich web applications.
The full list of valid WAI-ARIA roles is available at: https://www.w3.org/TR/wai-aria/#roles_categorization
attributeBindings public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:35
A list of properties of the view to apply as attributes. If the property is a string value, the value of that string will be applied as the value for an attribute of the property's name.
The following example creates a tag like <div priority="high" />
.
import Component from '@ember/component';
export default Component.extend({
attributeBindings: ['priority'],
priority: 'high'
});
If the value of the property is a Boolean, the attribute is treated as
an HTML Boolean attribute. It will be present if the property is true
and omitted if the property is false
.
The following example creates markup like <div visible />
.
import Component from '@ember/component';
export default Component.extend({
attributeBindings: ['visible'],
visible: true
});
If you would prefer to use a custom value instead of the property name, you can create the same markup as the last example with a binding like this:
import Component from '@ember/component';
export default Component.extend({
attributeBindings: ['isVisible:visible'],
isVisible: true
});
This list of attributes is inherited from the component's superclasses, as well.
classNameBindings public
Inherited from Ember.ClassNamesSupport packages/@ember/-internals/views/lib/mixins/class_names_support.ts:48
A list of properties of the view to apply as class names. If the property is a string value, the value of that string will be applied as a class name.
// Applies the 'high' class to the view element
import Component from '@ember/component';
Component.extend({
classNameBindings: ['priority'],
priority: 'high'
});
If the value of the property is a Boolean, the name of that property is added as a dasherized class name.
// Applies the 'is-urgent' class to the view element
import Component from '@ember/component';
Component.extend({
classNameBindings: ['isUrgent'],
isUrgent: true
});
If you would prefer to use a custom value instead of the dasherized property name, you can pass a binding like this:
// Applies the 'urgent' class to the view element
import Component from '@ember/component';
Component.extend({
classNameBindings: ['isUrgent:urgent'],
isUrgent: true
});
If you would like to specify a class that should only be added when the property is false, you can declare a binding like this:
// Applies the 'disabled' class to the view element
import Component from '@ember/component';
Component.extend({
classNameBindings: ['isEnabled::disabled'],
isEnabled: false
});
This list of properties is inherited from the component's superclasses as well.
classNames public
Inherited from Ember.ClassNamesSupport packages/@ember/-internals/views/lib/mixins/class_names_support.ts:36
Standard CSS class names to apply to the view's outer element. This property automatically inherits any class names defined by the view's superclasses as well.
concatenatedProperties public
Inherited from CoreObject packages/@ember/object/core.ts:355
Defines the properties that will be concatenated from the superclass (instead of overridden).
By default, when you extend an Ember class a property defined in
the subclass overrides a property with the same name that is defined
in the superclass. However, there are some cases where it is preferable
to build up a property's value by combining the superclass' property
value with the subclass' value. An example of this in use within Ember
is the classNames
property of Component
from @ember/component
.
Here is some sample code showing the difference between a concatenated property and a normal one:
import EmberObject from '@ember/object';
const Bar = EmberObject.extend({
// Configure which properties to concatenate
concatenatedProperties: ['concatenatedProperty'],
someNonConcatenatedProperty: ['bar'],
concatenatedProperty: ['bar']
});
const FooBar = Bar.extend({
someNonConcatenatedProperty: ['foo'],
concatenatedProperty: ['foo']
});
let fooBar = FooBar.create();
fooBar.get('someNonConcatenatedProperty'); // ['foo']
fooBar.get('concatenatedProperty'); // ['bar', 'foo']
This behavior extends to object creation as well. Continuing the above example:
let fooBar = FooBar.create({
someNonConcatenatedProperty: ['baz'],
concatenatedProperty: ['baz']
})
fooBar.get('someNonConcatenatedProperty'); // ['baz']
fooBar.get('concatenatedProperty'); // ['bar', 'foo', 'baz']
Adding a single property that is not an array will just add it in the array:
let fooBar = FooBar.create({
concatenatedProperty: 'baz'
})
view.get('concatenatedProperty'); // ['bar', 'foo', 'baz']
Using the concatenatedProperties
property, we can tell Ember to mix the
content of the properties.
In Component
the classNames
, classNameBindings
and
attributeBindings
properties are concatenated.
This feature is available for you to use throughout the Ember object model, although typical app developers are likely to use it infrequently. Since it changes expectations about behavior of properties, you should properly document its usage in each individual concatenated property (to not mislead your users to think they can override the property in a subclass).
element public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:166
Returns the current DOM element for the view.
elementId public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:148
The HTML id
of the component's element in the DOM. You can provide this
value yourself but it must be unique (just as in HTML):
{{my-component elementId="a-really-cool-id"}}
<MyComponent @elementId="a-really-cool-id" />
If not manually set a default value will be provided by the framework.
Once rendered an element's elementId
is considered immutable and you
should never change it. If you need to compute a dynamic value for the
elementId
, you should do this when the component or element is being
instantiated:
export default Component.extend({
init() {
this._super(...arguments);
var index = this.get('index');
this.set('elementId', `component-id${index}`);
}
});
isDestroyed public
Inherited from CoreObject packages/@ember/object/core.ts:504
Destroyed object property flag.
if this property is true
the observers and bindings were already
removed by the effect of calling the destroy()
method.
isDestroying public
Inherited from CoreObject packages/@ember/object/core.ts:522
Destruction scheduled flag. The destroy()
method has been called.
The object stays intact until the end of the run loop at which point
the isDestroyed
flag is set.
layout public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:1112
Layout can be used to wrap content in a component.
mergedProperties public
Inherited from CoreObject packages/@ember/object/core.ts:429
Defines the properties that will be merged from the superclass (instead of overridden).
By default, when you extend an Ember class a property defined in
the subclass overrides a property with the same name that is defined
in the superclass. However, there are some cases where it is preferable
to build up a property's value by merging the superclass property value
with the subclass property's value. An example of this in use within Ember
is the queryParams
property of routes.
Here is some sample code showing the difference between a merged property and a normal one:
import EmberObject from '@ember/object';
const Bar = EmberObject.extend({
// Configure which properties are to be merged
mergedProperties: ['mergedProperty'],
someNonMergedProperty: {
nonMerged: 'superclass value of nonMerged'
},
mergedProperty: {
page: { replace: false },
limit: { replace: true }
}
});
const FooBar = Bar.extend({
someNonMergedProperty: {
completelyNonMerged: 'subclass value of nonMerged'
},
mergedProperty: {
limit: { replace: false }
}
});
let fooBar = FooBar.create();
fooBar.get('someNonMergedProperty');
// => { completelyNonMerged: 'subclass value of nonMerged' }
//
// Note the entire object, including the nonMerged property of
// the superclass object, has been replaced
fooBar.get('mergedProperty');
// => {
// page: {replace: false},
// limit: {replace: false}
// }
//
// Note the page remains from the superclass, and the
// `limit` property's value of `false` has been merged from
// the subclass.
This behavior is not available during object create
calls. It is only
available at extend
time.
In Route
the queryParams
property is merged.
This feature is available for you to use throughout the Ember object model, although typical app developers are likely to use it infrequently. Since it changes expectations about behavior of properties, you should properly document its usage in each individual merged property (to not mislead your users to think they can override the property in a subclass).
positionalParams public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:991
Available since v1.13.0
Enables components to take a list of parameters as arguments.
For example, a component that takes two parameters with the names
name
and age
:
import Component from '@ember/component';
let MyComponent = Component.extend();
MyComponent.reopenClass({
positionalParams: ['name', 'age']
});
export default MyComponent;
It can then be invoked like this:
{{my-component "John" 38}}
The parameters can be referred to just like named parameters:
Name: {{name}}, Age: {{age}}.
Using a string instead of an array allows for an arbitrary number of parameters:
import Component from '@ember/component';
let MyComponent = Component.extend();
MyComponent.reopenClass({
positionalParams: 'names'
});
export default MyComponent;
It can then be invoked like this:
{{my-component "John" "Michael" "Scott"}}
The parameters can then be referred to by enumerating over the list:
{{#each names as |name|}}{{name}}{{/each}}
tagName public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:378
Tag name for the view's outer element. The tag name is only used when an
element is first created. If you change the tagName
for an element, you
must destroy and recreate the view element.
By default, the render buffer will use a <div>
tag for views.
If the tagName is ''
, the view will be tagless, with no outer element.
Component properties that depend on the presence of an outer element, such
as classNameBindings
and attributeBindings
, do not work with tagless
components. Tagless components cannot implement methods to handle events,
and their element
property has a null
value.
didInsertElement public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:308
Called when the element of the view has been inserted into the DOM. Override this function to do any set up that requires an element in the document body.
When a view has children, didInsertElement will be called on the child view(s) first and on itself afterwards.
didReceiveAttrs public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:53
Available since v1.13.0
Called when the attributes passed into the component have been updated. Called both during the initial render of a container and during a rerender. Can be used in place of an observer; code placed here will be executed every time any attribute updates.
didRender public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:72
Available since v1.13.0
Called after a component has been rendered, both on initial render and in subsequent rerenders.
didUpdate public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:140
Available since v1.13.0
Called when the component has updated and rerendered itself. Called only during a rerender, not during an initial render.
didUpdateAttrs public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:106
Available since v1.13.0
Called when the attributes passed into the component have been changed. Called only during a rerender, not during an initial render.
willClearRender public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:321
Called when the view is about to rerender, but before anything has been torn down. This is a good opportunity to tear down any manual observers you have installed based on the DOM state
willDestroyElement public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:358
Called after the element of the view is destroyed.
willInsertElement public
Inherited from Ember.ViewMixin packages/@ember/-internals/views/lib/mixins/view_support.ts:300
Called when a view is going to insert an element into the DOM.
willRender public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:89
Available since v1.13.0
Called before a component has been rendered, both on initial render and in subsequent rerenders.
willUpdate public
Defined in packages/@ember/-internals/glimmer/lib/component.ts:123
Available since v1.13.0
Called when the component is about to update and rerender itself. Called only during a rerender, not during an initial render.