GitHub
Twitterserialize
Defines custom serialization behavior for a property.
Boolean
Specifies if the property should be serialized. By default, all properties except for ones with defined getters are serialized. Prevent a property from being serialized like:
{
propertyName: {
serialize: false
}
}
Make a getter property part of the serialized result like:
{
propertyName: {
get: function() { /* ... */ },
serialize: true
}
}
serialize( currentValue, propertyName )
Specifies the serialized value of a property.
Parameters
- currentValue
{*}:The current value of the attribute.
- propertyName
{String}:The name of the property being serialized.
Returns
{*|undefined}:
If undefined is returned, the value is not serialized.
Use
serialize is useful for serializing an instance into a more JSON-friendly form. This can be used for many reasons, including saving a can-connected instance on the server or serializing [can-route.map can-route.map]'s internal map for display in the hash or pushstate URL.
The serialize property allows an opportunity to define how each property will behave when the instance is serialized. This can be useful for:
- serializing complex types like dates, arrays, or objects into string formats
- causing certain properties to be ignored when serialize is called
The following causes a locationIds property to be serialized into the comma separated ID values of the location property on this instance:
{
locationIds: {
serialize: function() {
return this.locations.map( function( location ) {
ids.push( location.id );
} ).join( "," );
}
}
}
Returning undefined for any property means this property will not be part of the serialized
object. For example, if the property numPages is not greater than zero, the following example
won't include it in the serialized object.
{
prop: {
numPages: {
serialize: function( num ) {
if ( num <= 0 ) {
return undefined;
}
return num;
}
}
}
}