Ember Parachute

Philosophy

@voll/ember-parachute is an addon that improves upon the experience of working with
query params in Ember. Instead of defining query params in both your route and controller, with this addon you can define them in one place as a query param map/object.

This map is the source of truth for your query params, and will generate a mixin that you can then add into your controller. The mixin adds very helpful properties and methods that makes working with query params a breeze!

* Ember.js v3.24 or above
* Ember CLI v3.24 or above
* Node.js v12 or above

One important point about this addon is that it is opinionated about _where_ the data is fetched. In a traditional query params setup, your route is responsible for fetching data in its model hook. With this addon, the responsibility moves into the controller. The benefit of this approach is that data fetching no longer blocks your UI from loading, and paves the way for advanced UX such as ["skeleton loading"][skeleton-loading].

Installation

``
ember install @voll/ember-parachute
`

Helpful Links

- ### [Live Demo][demo]
- ### [Changelog][changelog]

Looking for help?

If it is a bug please open an issue on GitHub.

Usage

The source of truth for your application's query params are query param maps. First, define one in your controller:

`js
import Controller from '@ember/controller';
import QueryParams from '@voll/ember-parachute';
import { or } from '@ember/object/computed';

export const myQueryParams = new QueryParams({
parachuteOpen: {
as: 'parachute',
defaultValue: true
},
page: {
defaultValue: 1,
refresh: true,
replace: true
},
search: {
defaultValue: '',
refresh: true
},
tags: {
defaultValue: ['Ember', 'Parachute'],
serialize(value) {
return value.toString();
},
deserialize(value = '') {
return value.split(',');
}
}
});

export default Controller.extend(myQueryParams.Mixin, {
queryParamsChanged: or('queryParamsState.{page,search,tags}.changed'),

setup({ queryParams }) {
this.fetchData(queryParams);
},

queryParamsDidChange({ shouldRefresh, queryParams }) {
// if any query param with refresh: true is changed, shouldRefresh is true
if (shouldRefresh) {
this.fetchData(queryParams);
}
},

reset({ queryParams }, isExiting) {
if (isExiting) {
this.resetQueryParams();
}
},

fetchData(queryParams) {
// fetch data
},

actions: {
resetAll() {
// reset all query params to their default values specified in the query param map
this.resetQueryParams();
}
}
});
`

In the above example, the mixin adds the setup, reset, and queryParamsDidChange hooks. You can use these hooks to perform tasks like fetching data based on the query params or resetting them when leaving the route. Additionally, you can create a computed property observing queryParamsState that will allow you to display a button in your UI that can clear all query params via resetQueryParams.

Please continue reading for more advanced usage.

Decorators

This package provides some decorators in order to use @voll/ember-parachute with the now supported class syntax.

$3

`js
import Controller from '@ember/controller';
import { queryParam } from '@voll/ember-parachute/decorators';

export default class MyController extends Controller {
@queryParam({
as: 'parachute',
serialize(value) {
return value ? 'open' : 'closed';
},
deserialize(value) {
return value === 'open' ? true : false;
}
})
parachuteOpen = true;

@queryParam({ refresh: true, replace: true }) page = 1;

@queryParam({ refresh: true }) search = '';

@queryParam({
refresh: true,
serialize(value = '') {
return value.toString();
},
deserialize(value = '') {
return value.split(',');
}
})
tags = ['Ember', 'Parachute'];
}
`

$3

If you're not using any query params but still want the setup and reset hooks, you can use the withParachute class decorator.

`js
import Controller from '@ember/controller';
import { withParachute } from '@voll/ember-parachute/decorators';

@withParachute
export default class MyController extends Controller {
setup() {}
reset() {}
}
`

Query Param Map

The query param map is the source of truth for your query params. Here, you'll be able to define configuration for each query param:

`js
import QueryParams from '@voll/ember-parachute';

const myQueryParams = new QueryParams({
direction: {
as: 'dir',
defaultValue: 'asc',
refresh: true
},
page: {
defaultValue: 1,
refresh: true,
replace: true
},
search: {
defaultValue: '',
refresh: true
}
});
`

Each query param is defined as follows (using TypeScript notation for documenting types):

`ts
interface QueryParamOption {
as?: string;
defaultValue?: any;
refresh?: boolean;
replace?: boolean;
scope?: 'controller';
serialize?(value: any): any;
deserialize?(value: any): any;
}
`

For example:

`js
direction: {
as: 'dir',
defaultValue: 'asc',
refresh: true,
scope: 'controller',
serialize(value) {
return value;
},
deserialize(value) {
return value;
}
}
`

$3

The as option lets you optionally override the query param URL key for a query param. By default this will be the same as the key in the query param map.

$3

Required. The defaultValue option specifies the default value for the query param. When a query param is set to its default value, it will not appear in the URL.

$3

When refresh is true, the queryParamsDidChange hook provided by the mixin will notify you when a refreshable query param has changed. You can use that value to determine whether or not you need to refetch data.

$3

By default, Ember will use pushState to update the URL in the address bar in response to a controller query param property change, but when replace is true it will use replaceState instead (which prevents an additional item from being added to your browser's history).

$3

scope can only be one value if specified: controller. This is equivalent to the scope option in regular Ember query params. You can read more about it in the bottom paragraph [here][ember-qp-docs].

$3

An optional function that lets you serialize or format a value before it is updated in the URL. For example, if your query param represents an array of values, you could do the following to avoid having the [ and ] being included into the URL:

`js
tags: {
defaultValue: ['Ember', 'Parachute'],
serialize(value) {
return value.toString();
},
deserialize(value = '') {
return value.split(',');
}
}
`

The above will show ?tags=Ember,Parachute (before encoding) in the URL. When you get the value though, it is still an array:

`js
controller.get('tags'); // ['Ember', 'Parachute']
`

$3

If you provide a serialize function, you will need to include a deserialize as well. This function will be used to transform the value in the URL back into the value your controller receives.

For example:

`js
showReadme: {
as: 'readme',
defaultValue: true,
serialize(value) {
return value ? 'yes' : 'no';
},
deserialize(value) {
return value === 'yes' ? true : false;
}
}
`

Your controller value for showReadme will still be true or false, even though it is displayed in your URL as ?showReadme=yes.

$3

The Query Param Map not only accepts multiple arguments, but it can also be extended.

`js
import QueryParams from '@voll/ember-parachute';

const SortParams = {
sortName: {
defaultValue: 'name',
refresh: true
},
sortDirection: {
defaultValue: 'asc',
refresh: true
}
};

const SearchParams = {
query: {
defaultValue: '',
refresh: true
}
};

const myQueryParams = new QueryParams(SortParams, SearchParams /, ... /);

const myExtendedQueryParams = myQueryParams.extend(
{
sidebarOpen: {
defaultValue: true
}
} /, ... /
);
`

With the above code, the myExtendedQueryParams map will generate Query Params for sortName, sortDirection, query, and sidebarOpen.

Controller Mixin

After creating a query params map, you can generate a controller mixin with the Mixin property on the query params map:

`js
const myQueryParams = new QueryParams({
/ ... /
});

export default Controller.extend(myQueryParams.Mixin, {
// ...
});
`

The mixin adds the following to your controller:

$3

You can use this CP to get all query param values:

`js
controller.get('allQueryParams'); // { page: 2, direction: 'desc' };
`

This CP is useful in scenarios where you need to pass all query params as an option. For example, you could pass these into a link-to.

$3

This CP returns an object with information about the state of your query params.

`js
controller.get('queryParamsState.page'); // { value: 2, defaultValue: 1, changed: true }
`

This CP is useful when creating another CP to determine if any query params have changed from their default values:

`js
queryParamsChanged: or('queryParamsState.{page,search,tags}.changed');
`

You can then use this CP to conditionally display a button that can clear all query params to their default values.

$3

All hooks will receives a ParachuteEvent as an argument which can be defined as:

`ts
// what changed
interface QueryParamsChanged {
[queryParamKey: string]: string;
}

// all changes
interface QueryParamsChanges {
[queryParamKey: string]: string;
}

// all query param values
interface QueryParams {
[queryParamKey: string]: any;
}

interface ParachuteEvent {
changes: QueryParamsChanges;
changed: QueryParamsChanged;
queryParams: QueryParams;
routeName: string;
shouldRefresh: boolean;
}
`

$3

`ts
function queryParamsDidChange(queryParamsChangedEvent: ParachuteEvent): void;
`

`js
export default Controller.extend(myQueryParams.Mixin, {
queryParamsDidChange({
routeName,
shouldRefresh,
queryParams,
changed,
changes
}) {
if (shouldRefresh) {
// refetch data
}

if (changed.myQueryParamKey) {
// do something special
}
}
});
`

$3

`ts
function setup(queryParamsChangedEvent: ParachuteEvent): void;
`

`js
export default Controller.extend(myQueryParams.Mixin, {
setup({ routeName, shouldRefresh, queryParams, changed, changes }) {
// Fetch some initial data & setup the controller
}
});
`

> Note: If you've overridden your route's setupController, you must use this._super(...arguments); in setupController for the setup hook to fire.

$3

`ts
function reset(
queryParamsChangedEvent: ParachuteEvent,
isExiting: boolean
): void;
`

`js
export default Controller.extend(myQueryParams.Mixin, {
reset(
{ routeName, shouldRefresh, queryParams, changed, changes },
isExiting
) {
if (isExiting) {
this.resetQueryParams();
}
}
});
`

> Note: If you've overridden your route's resetController, you must use this._super(...arguments); in resetController for the reset hook to fire.

$3

The controller also emits an event for each hook which receives the same arguments:

`ts
export default Controller.extend({
onChange: on('queryParamsDidChange', function(
queryParamsChangedEvent: ParachuteEvent
) {
// ...
}),

onSetup: on('setup', function(queryParamsChangedEvent: ParachuteEvent) {
// ...
}),

onReset: on('reset', function(
queryParamsChangedEvent: ParachuteEvent,
isExiting: boolean
) {
// ...
})
});
`

For example, you can use this in conjunction with [ember-metrics][ember-metrics] to track when query params were changed:

`js
this.get('metrics').trackEvent(
Object.assign(
{
event: 'Query Params Changed',
routeName: routeName
},
queryParams
)
);
`

$3

`ts
function resetQueryParams(params?: string[]): void;
`

Reset all or given params to their default value. The second argument is an array of query params to reset. If empty, all query params will be reset. You can use this in an action to reset query params when they have changed:

`js
export default Controller.extend(myQueryParams.Mixin, {
queryParamsChanged: or('queryParamsState.{page,search,tags}.changed'),

actions: {
resetAll() {
this.resetQueryParams();
}
}
});
`

`hbs
{{#button onClick=(action "resetAll") disabled=(not queryParamsChanged)}}
Reset All
{{/button}}
`

> Note: This method works well in conjunction with setDefaultQueryParamValue.

$3

`ts
function setDefaultQueryParamValue(key: string, defaultValue: any): void;
`

Set the default value for a given param. An example where this is useful is where you need to fetch default values from elsewhere (e.g. your API).

`js
controller.setDefaultQueryParamValue('search', 'foo');
controller.setDefaultQueryParamValue('direction', 'asc');
`

If you set a new default value after the existing default has been promoted to the value, like when calling setDefaultQueryParamValue in the setup hook, you need to call resetQueryParams to apply those new defaults as the values. You can do this for all QPs or for a single one via resetQueryParams(['nameOfQp'])`.

NOTE: Changing the defaultValue at any point will not clear the query parameter from being shown in the URI. We do not have control over that as it is private API.

[changelog]: CHANGELOG.md
[ember-metrics]: https://github.com/poteto/ember-metrics
[ember-qp-docs]: https://guides.emberjs.com/v2.14.0/routing/query-params/
[skeleton-loading]: https://emberway.io/skeleton-screen-loading-in-ember-js-2f7ac2384d63