Simple, highly configurable flash messages for ember-cli.
This ember-cli
addon adds a simple flash message service and component to your app. Just inject with Ember.inject.service
and you're good to go!
ember install ember-cli-flash
This addon is tested against the release
, beta
and canary
channels, ~1.11.0
, and 1.12.1
. Because this addon makes use of attribute bindings, which were introduced in ember 1.11.0
, earlier versions of ember are not compatible with the latest version.
Usage is very simple. First, add one of the template examples to your app. Then, inject the flashMessages
service and use one of its convenience methods:
import Component from '@ember/component';
import { inject } from '@ember/service';
export default Component.extend({
flashMessages: inject()
});
You can quickly add flash messages using these methods from the service:
.success
.warning
.info
.danger
.success
.warning
.info
.alert
.secondary
These will add the appropriate classes to the flash message component for styling in Bootstrap or Foundation. For example:
// Bootstrap: the flash message component will have 'alert alert-success' classes
// Foundation: the flash message component will have 'alert-box success' classes
import { get } from '@ember/object';
get(this, 'flashMessages').success('Success!');
You can take advantage of Promises, and their .then
and .catch
methods. To add a flash message after saving a model (or when it fails):
import { get } from '@ember/object';
actions: {
saveFoo() {
const flashMessages = get(this, 'flashMessages');
Ember.get(this, 'model')
.save()
.then((res) => {
flashMessages.success('Successfully saved!');
doSomething(res);
})
.catch((err) => {
flashMessages.danger('Something went wrong!');
handleError(err);
});
}
}
If the convenience methods don't fit your needs, you can add custom messages with add
:
import { get } from '@ember/object';
get(this, 'flashMessages').add({
message: 'Custom message'
});
You can also pass in options to custom messages:
import { get } from '@ember/object';
get(this, 'flashMessages').add({
message: 'I like alpacas',
type: 'alpaca',
timeout: 500,
priority: 200,
sticky: true,
showProgress: true,
extendedTimeout: 500,
destroyOnClick: false,
onDestroy() {
// behavior triggered when flash is destroyed
}
});
get(this, 'flashMessages').success('This is amazing', {
timeout: 100,
priority: 100,
sticky: false,
showProgress: true
});
-
message: string
Required when
preventDuplicates
is enabled. The message that the flash message displays. -
type?: string
Default:
info
This is mainly used for styling. The flash message's
type
is set as a class name on the rendered component, together with a prefix. The rendered class name depends on the message type that was passed into the component. -
timeout?: number
Default:
3000
Number of milliseconds before a flash message is automatically removed.
-
priority?: number
Default:
100
Higher priority messages appear before low priority messages. The best practise is to use priority values in multiples of
100
(100
being the lowest priority). Note that you will need modify your template for this work. -
sticky?: boolean
Default:
false
By default, flash messages disappear after a certain amount of time. To disable this and make flash messages permanent (they can still be dismissed by click), set
sticky
to true. -
showProgress?: boolean
Default:
false
To show a progress bar in the flash message, set this to true.
-
extendedTimeout?: number
Default:
0
Number of milliseconds before a flash message is removed to add the class 'exiting' to the element. This can be used to animate the removal of messages with a transition.
-
destroyOnClick?: boolean
Default:
true
By default, flash messages will be destroyed on click. Disabling this can be useful if the message supports user interaction.
-
onDestroy: function
Default:
undefined
A function to be called when the flash message is destroyed.
To animate messages, set extendedTimeout
to something higher than zero. Here we've chosen 500ms.
module.exports = function(environment) {
var ENV = {
flashMessageDefaults: {
extendedTimeout: 500
}
}
}
Then animate using CSS transitions, using the .active
and .active.exiting
classes.
.alert {
opacity: 0;
position: relative;
left: 100px;
transition: all 700ms cubic-bezier(0.68, -0.55, 0.265, 1.55);
&.active {
opacity: 1;
left: 0px;
&.exiting {
opacity: 0;
left: 100px;
}
}
}
You can also add arbitrary options to messages:
import { get } from '@ember/object';
get(this, 'flashMessages').success('Cool story bro', {
someOption: 'hello'
});
get(this, 'flashMessages').add({
message: 'hello',
type: 'foo',
componentName: 'some-component',
content: customContent
});
This makes use of the component helper, allowing the template that ultimately renders the flash to be dynamic:
It's best practice to use flash messages sparingly, only when you need to notify the user of something. If you're sending too many messages, and need a way for your users to clear all messages from screen, you can use this method:
import { get } from '@ember/object';
get(this, 'flashMessages').clearMessages();
The flash message service is designed to be Fluent, allowing you to chain methods on the service easily. The service should handle most cases but if you want to access the flash object directly, you can use the getFlashObject
method:
import { get } from '@ember/object';
const flashObject = get(this, 'flashMessages').add({
message: 'hola',
type: 'foo'
}).getFlashObject();
You can then manipulate the flashObject
directly. Note that getFlashObject
must be the last method in your chain as it returns the flash object directly.
In config/environment.js
, you can override service defaults in the flashMessageDefaults
object:
module.exports = function(environment) {
var ENV = {
flashMessageDefaults: {
// flash message defaults
timeout: 5000,
extendedTimeout: 0,
priority: 200,
sticky: true,
showProgress: true,
// service defaults
type: 'alpaca',
types: [ 'alpaca', 'notice', 'foobar' ],
preventDuplicates: false
}
}
}
See the options section for information about flash message specific options.
-
type?: string
Default:
info
When adding a custom message with
add
, if notype
is specified, this default is used. -
types?: array
Default:
[ 'success', 'info', 'warning', 'danger', 'alert', 'secondary' ]
This option lets you specify exactly what types you need, which means in the above example, you can do
Ember.get('flashMessages').{alpaca,notice,foobar}
. -
preventDuplicates?: boolean
Default:
false
If
true
, only 1 instance of a flash message (based on itsmessage
) can be added at a time. For example, adding two flash messages with the message"Great success!"
would only add the first instance into the queue, and the second is ignored.
Then, to display somewhere in your app, add this to your template:
It also accepts your own template:
The close
action is always passed to the component whether it is used or not. It can be used to implement your own close button, such as an x
in the top-right corner.
When using a custom close
action, you will want to set destroyOnClick=false
to override the default (destroyOnClick=true
). You could do this globally in flashMessageDefaults
.
{{#each flashMessages.queue as |flash|}}
{{#flash-message flash=flash as |component flash close|}}
{{flash.message}}
<a href="#" {{action close}}>x</a>
{{/flash-message}}
{{/each}}
By default, flash messages will have Bootstrap style class names. If you want to use Foundation, simply specify the messageStyle
on the component:
To display messages sorted by priority, add this to your template:
To add radius
or round
type corners in Foundation:
If the provided component isn't to your liking, you can easily create your own. All you need to do is pass in the flash
object to that component:
When you install the addon, it should automatically generate a helper located at tests/helpers/flash-message.js
. You can do this manually as well:
$ ember generate ember-cli-flash
This also adds the helper to tests/test-helper.js
. You won't actually need to import this into your tests, but it's good to know what the blueprint does. Basically, the helper overrides the _setInitialState
method so that the flash messages behave intuitively in a testing environment.
An example acceptance test:
// tests/acceptance/foo-test.js
test('flash message is rendered', function(assert) {
assert.expect(1);
visit('/');
andThen(() => assert.ok(find('.alert.alert-success').length));
});
An example integration test:
// tests/integration/components/x-foo-test.js
import { getOwner } from '@ember/application';
moduleForComponent('x-foo', 'Integration | Component | x foo', {
integration: true,
beforeEach() {
//We have to register any types we expect to use in this component
const typesUsed = ['info', 'warning', 'success'];
getOwner(this).lookup('service:flash-messages').registerTypes(typesUsed);
}
});
test('it renders', function(assert) {
...
});
For unit tests that require the flashMessages
service, you'll need to do a small bit of setup:
import { getOwner } from '@ember/application';
moduleFor('route:foo', 'Unit | Route | foo', {
needs: ['service:flash-messages'],
beforeEach() {
const typesUsed = ['warning', 'success'];
getOwner(this).lookup('service:flash-messages').registerTypes(typesUsed);
}
});
This addon is minimal and does not currently ship with a stylesheet. You can style flash messages by targeting the appropriate alert class (Foundation or Bootstrap) in your CSS.
git clone https://github.com/poteto/ember-cli-flash.git
cd my-addon
yarn install
yarn run lint:js
yarn run lint:js -- --fix
ember test
– Runs the test suite on the current Ember versionember test --server
– Runs the test suite in "watch mode"yarn test
– Runsember try:each
to test your addon against multiple Ember versions
ember serve
- Visit the dummy application at http://localhost:4200.
For more information on using ember-cli, visit https://www.ember-cli.com/.