@ngneat/bind-query-params-patch
v1.0.3
Published
Sync URL Query Params with Angular Form Controls
Downloads
3
Maintainers
Readme
Sync URL Query Params with Angular Form Controls
The library provides a simple and reusable solution for binding URL query params to Angular Forms
Demo
Installation
npm install @ngneat/bind-query-params
Usage
Inject the BindQueryParamsFactory
provider, pass an array of definitions and connect
it to your form:
import { BindQueryParamsFactory } from '@ngneat/bind-query-params';
interface Filters {
searchTerm: string;
someBoolean: boolean;
}
@Component({
template: `Your normal form setup`,
})
export class MyComponent {
filters = new FormGroup({
searchTerm: new FormControl(),
someBoolean: new FormControl(false),
});
bindQueryParamsManager = this.factory
.create<Filters>([
{ queryKey: 'searchTerm' },
{ queryKey: 'someBoolean', type: 'boolean' }
]).connect(this.filters);
constructor(private factory: BindQueryParamsFactory) {}
ngOnDestroy() {
this.bindQueryParamsManager.destroy();
}
}
With this setup, the manager
will take care of two things:
- Update the
control
's value when the page is loaded for the first time - Update the URL query parameter when the corresponding
control
value changes
QueryParam Definition
queryKey
The query parameter key
path
The form control path. If it is not specified, the manager assumes that the path
is the queryKey
. We can also pass nested keys, for example, person.name
:
{ queryKey: 'name', path: 'person.name' }
type
Specify the control value type. Available options are:
boolean
, array
, number
, string
and object
.
Before updating the control with the value, the manager will parse it based on the provided type
.
parser
Provide a custom parser. For example, the default array
parser converts the value to an array
of strings. If we need it to be an array of numbers, we can pass the following parser
:
const def = { parser: (value) => value.split(',').map((v) => +v) };
serializer
Provide a custom serializer. For example, supposing that we have a FormControl
that carries a Date and we want to persist, in the query params, a custom value, such as a string
Date, we can do something like the following serializer
:
const def = { serializer: (value) => (value instanceof Date ? value.toISOString().slice(0, 10) : (value as string)) };
strategy
twoWay
The default strategy is twoWay
, which means that query parameters get synced once with the form group, and any subsequent form value changes are synced with the URL.
modelToUrl
As we work with async control values, such as a dropdown list with its options coming from the server, we cannot immediately update the control. When this occurs, we can use the modelToUrl
strategy, which doesn't update the control value when the page loads.
Once the data is available, we can call the manager.syncDefs()
or manager.syncAllDefs()
methods to update the controls based on the current query parameters:
@Component()
export class MyComponent {
filters = new FormGroup({
searchTerm: new FormControl(),
users: new FormControl([]),
someBoolean: new FormControl(false),
});
bindQueryParamsManager = this.factory
.create<Filters>([
{ queryKey: 'searchTerm' },
{ queryKey: 'someBoolean', type: 'boolean' },
{ queryKey: 'users', type: 'array', strategy: 'modelToUrl' },
])
.connect(this.filters);
constructor(private factory: BindQueryParamsFactory) {}
ngOnInit() {
service.getUsers().subscribe((users) => {
// Initalize the dropdown
this.users = users;
// Sync specific controls use:
this.manager.syncDefs('users');
// Sync all controls
this.manager.syncAllDefs();
});
}
ngOnDestroy() {
this.bindQueryParamsManager.destroy();
}
}
Note that syncDefs
will always be called once under the hood.
Browser Support
The library uses the URLSearchParams API, which supported in any browser except IE.
Contributors ✨
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!