set
Specify what happens when a property value is set.
set( [newVal,] [resolve] )
NOTE: Instead of using
set
to set the values of other properties, use the value behavior.
A set function defines the behavior of what happens when a value is set on an instance. It is typically used to:
- Add or update other properties as side effects
- Coerce the set value into an appropriate action
The behavior of the setter depends on the number of arguments specified. This means that a setter like:
{
prop: {
set: function() {}
}
}
behaves differently than:
{
prop: {
set: function( newVal ) {}
}
}
Parameters
- newVal
{*}
:The type function coerced value the user intends to set on the instance.
- resolve
{function(newValue)}
:A callback that can set the value of the property asynchronously.
Returns
{*|undefined}
:
If a non-undefined value is returned, that value is set as the attribute value.
If an undefined
value is returned, the behavior depends on the number of
arguments the setter declares:
- If the setter does not specify the
newValue
argument, the property value is set to the type converted value. - If the setter specifies the
newValue
argument only, the attribute value will be set toundefined
. - If the setter specifies both
newValue
andresolve
, the value of the property will not be updated untilresolve
is called.
Use
A property's set
function can be used to customize the behavior of when an attribute value is set. Let's see some common cases:
Side effects
The following makes setting a page
property update the offset
:
import {DefineMap} from "can";
const Pages = DefineMap.extend( {
limit: { default: 5 },
offset: { default: 0 },
page: {
set: function( newVal ) {
this.offset = ( parseInt( newVal ) - 1 ) * this.limit;
}
}
} );
const book = new Pages();
book.page = 10;
console.log( book.offset ); //-> 45
The following makes changing makeId
un-define the modelId
property:
import {DefineMap} from "can";
const Car = DefineMap.extend( {
modelId: { default: undefined },
makeId: {
set: function(newValue){
// Check if we are changing.
if(newValue !== this.makeId) {
this.modelId = undefined;
}
// Must return value to set as we have a `newValue` argument.
return newValue;
}
}
} );
const myCar = new Car({ makeId: "GMC", modelId: "Jimmy" });
console.log( myCar.modelId ); //-> "Jimmy"
myCar.makeId = "Chevrolet";
console.log( myCar.modelId ); //-> undefined
Asynchronous Setter
The following shows an async setter:
{
prop: {
set: function( newVal, setVal ) {
$.get( "/something", {}, setVal );
}
}
}
Behavior depends on the number of arguments.
When a setter returns undefined
, its behavior changes depending on the number of arguments.
With 0 arguments, the original set value is set on the attribute.
import {DefineMap} from "can";
const MyMap = DefineMap.extend( {
prop: { set: function() {} }
} );
const map = new MyMap( { prop: "foo" } );
console.log( map.prop ); //-> "foo"
With 1 argument, an undefined
return value will set the property to undefined
.
import {DefineMap} from "can";
const MyMap = DefineMap.extend( {
prop: { set: function( newVal ) {} }
} );
const map = new MyMap( { prop: "foo" } );
console.log( map.prop ); //-> undefined
With 2 arguments, undefined
leaves the property in place. It is expected
that resolve
will be called:
import {DefineMap} from "can";
const MyMap = DefineMap.extend( {
prop: {
set: function( newVal, resolve ) {
resolve( newVal + "d" );
}
}
} );
const map = new MyMap( { prop: "foo" } );
console.log( map.prop ); //-> "food";
Side effects
A set function provides a useful hook for performing side effect logic as a certain property is being changed.
In the example below, Paginator DefineMap includes a page
property, which derives its value entirely from other properties (limit and offset). If something tries to set the page
directly, the set method will set the value of offset
:
import {DefineMap} from "can";
const Paginate = DefineMap.extend( {
limit: "number",
offset: "number",
page: {
set: function( newVal ) {
this.offset = ( parseInt( newVal ) - 1 ) * this.limit;
},
get: function() {
return Math.floor( this.offset / this.limit ) + 1;
}
}
} );
const p = new Paginate( { limit: 10, offset: 20 } );
console.log( p.offset ); //-> 20
console.log( p.page ); //-> 2
Merging
By default, if a value returned from a setter is an object the effect will be to replace the property with the new object completely.
import {DefineMap} from "can";
const Contact = DefineMap.extend( {
info: {
set: function( newVal ) {
return newVal;
}
}
} );
const alice = new Contact( {
info: { name: "Alice Liddell", email: "alice@liddell.com" }
} );
const info = alice.info;
alice.info = { name: "Allison Wonderland", phone: "888-888-8888" };
console.log( info === alice.info ); // -> false
In contrast, you can merge properties with:
import {DefineMap} from "can";
const Contact = DefineMap.extend( {
info: {
set: function( newVal ) {
if ( this.info ) {
return this.info.set( newVal );
} else {
return newVal;
}
}
}
} );
const alice = new Contact( {
info: { name: "Alice Liddell", email: "alice@liddell.com" }
} );
const info = alice.info;
alice.info = { name: "Allison Wonderland", phone: "888-888-8888" };
console.log( info === alice.info ); // -> true
Batched Changes
By default, calls to set
methods are wrapped in a call to batch.start and batch.stop, so if a set method has side effects that set more than one property, all these sets are wrapped in a single batch for better performance.