So far, our app is directly showing the user data from our Ember Data models. As our app grows, we will want to manipulate data further before presenting it to our users. For this reason, Ember offers Handlebars template helpers to decorate the data in our templates. Let's use a handlebars helper to allow our users to quickly see if a property is "Standalone" or part of a "Community".
To get started, let's generate a helper for rental-property-type
:
ember g helper rental-property-type
This will create two files, our helper and its related test:
installing helper
create app/helpers/rental-property-type.js
installing helper-test
create tests/integration/helpers/rental-property-type-test.js
Our new helper starts out with some boilerplate code from the generator:
import { helper } from '@ember/component/helper';
export function rentalPropertyType(params/*, hash*/) {
return params;
}
export default helper(rentalPropertyType);
Let's update our rental-listing
component template to use our new helper and pass in rental.category
:
Ideally we'll see "Type: Standalone - Estate" for our first rental property.
Instead, our default template helper is returning back our rental.category
values.
Let's update our helper to look if a property exists in an array of communityPropertyTypes
,
if so, we'll return either 'Community'
or 'Standalone'
:
import { helper } from '@ember/component/helper';
export function rentalPropertyType(params/*, hash*/) {
return params;
}
const communityPropertyTypes = [
'Condo',
'Townhouse',
'Apartment'
];
export function rentalPropertyType([propertyType]) {
if (communityPropertyTypes.includes(propertyType)) {
return 'Community';
}
return 'Standalone';
}
export default helper(rentalPropertyType);
Each argument in the helper will be added to an array and passed to our helper. For example, {{my-helper "foo" "bar"}}
would result in myHelper(["foo", "bar"])
. Using array ES2015 destructuring assignment, we can name expected parameters within the array. In the example above, the first argument in the template will be assigned to propertyType
. This provides a flexible, expressive interface for your helpers, including optional arguments and default values.
Now in our browser we should see that the first rental property is listed as "Standalone", while the other two are listed as "Community".
Integration Test
Update the content of the integration test to the following to fix it:
import { module, test } from 'qunit';
import { setupRenderingTest } from 'ember-qunit';
import { render } from '@ember/test-helpers';
import hbs from 'htmlbars-inline-precompile';
module('Integration | Helper | my-helper', function(hooks) {
setupRenderingTest(hooks);
// Replace this with your real tests.
test('it renders', async function(assert) {
this.set('inputValue', '1234');
test('it renders correctly for a Standalone rental', async function(assert) {
this.set('inputValue', 'Estate');
await render(hbs`{{rental-property-type inputValue}}`);
assert.equal(this.element.textContent.trim(), '1234');
assert.equal(this.element.textContent.trim(), 'Standalone');
});
test('it renders correctly for a Community rental', async function(assert) {
this.set('inputValue', 'Apartment');
await render(hbs`{{rental-property-type inputValue}}`);
assert.equal(this.element.textContent.trim(), 'Community');
});
});