Overview

Use can-type to define rules around types to handle type checking and type conversion. Works well with can-define, [can-define-object], and [can-stache-define-element].

can-type specifies the following type functions:

type.maybe

Use maybe to specify a TypeObject which will accept a value that is a member of the provided type, or is undefined or null.

import { Reflect, type } from "can/everything";

const NumberType = type.maybe(Number);

let val = Reflect.convert(42, NumberType);
console.log(val); // -> 42

val = Reflect.convert(null, NumberType);
console.log(val); // -> null

val = Reflect.convert(undefined, NumberType);
console.log(val); // -> undefined

Reflect.convert("hello world", NumberType); // throws!

type.convert

Use convert to define a TypeObject which will coerce the value to the provided type.

import { Reflect, type } from "can/everything";

const NumberType = type.convert(Number);

let val = Reflect.convert("42", NumberType);
console.log(val); // -> 42

type.maybeConvert

Use maybeConvert to define a TypeObject which will coerce the value to the type, but also accept values of null and undefined.

import { Reflect, type } from "can/everything";

const DateType = type.maybeConvert(Date);

const date = new Date();

let val = Reflect.convert(date, DateType);
console.log(val); // -> date

val = Reflect.convert(null, DateType);
console.log(val); // -> null

val = Reflect.convert(undefined, DateType);
console.log(val); // -> undefined

val = Reflect.convert("12/04/1433", DateType);
console.log(val); // -> Date{12/04/1433}

type.check

Use check to specify a strongly typed TypeObject that verifies the value passed is of the same type.

import { Reflect, type } from "can/everything";

const StringType = type.check(String);

let val = Reflect.convert("hello world", StringType);
console.log(val); // -> hello world

Reflect.convert(42, StringType); // throws!

Creating Models and ViewModels

can-type is useful for creating typed properties in [can-define-object]. You might want to use stricter type checking for some properties or classes and looser type checking for others. The following creates properties with various properties and type methods:

import { DefineObject, type } from "can/everything";

class Person extends DefineObject {
  static define = {
    first: type.check(String), // type checking is the default behavior
    last: type.maybe(String),

    age: type.convert(Number),
    birthday: type.maybeConvert(Date)
  };
}

let fib = new Person({
  first: "Fibonacci",
  last: null,
  age: "80",
  birthday: undefined
});

console.log(fib); // ->Person{ ... }

Note: as mentioned in the comment above, type checking is the default behavior of [can-define-object], so first: type.check(String) could be written as first: String.

When creating models with can-rest-model you might want to be loose in the typing of properties, especially when working with external services you do not have control over.

On the other hand, when creating ViewModels for components, such as with [can-stache-define-element] you might want to be stricter about how properties are passed, to prevent mistakes.

import { StacheDefineElement, type } from "can/everything";

class Progress extends StacheDefineElement {
  static define = {
    value: {
      type: type.check(Number),
      default: 0
    },
    max: {
      type: type.check(Number),
      default: 100
    },
    get width() {
      let w = (this.value / this.max) * 100;
      return w + '%';
    }
  };

  static view = `
    <div style="background: black;">
      <span style="background: salmon; display: inline-block; width: {{width}}">&nbsp;</span>
    </div>
  `;
}

customElements.define("custom-progress-bar", Progress);

let progress = new Progress();
progress.value = 34;

document.body.append(progress);

function increment() {
  setTimeout(() => {
    if(progress.value < 100) {
      progress.value++;
      increment();
    }
  }, 500);
}

increment();

Note: Having both type: type.check(Number) and default: 0 in the same definition is redundant. Using default: 0 will automatically set up type checking. It is shown above for clarity.

See [can-stache-define-element] and [can-define-object] for more on these APIs.

How it works

The can-type methods work by creating functions that are compatible with canReflect.convert.

These functions have a can.new Symbol that points to a function that is responsible for creating an instance of the type. The following is an overview of how this function works:

1. Determine if value is already the correct type

• Maybe types (type.maybe, type.maybeConvert) will return true if the value is null or undefined.
• Common primitive types (Number, String, Boolean) will return true if typeof returns the correct result.
• Other types will return true if the value is an instanceof the type.
• TypeObjects (or anything with a can.isMember Symbol) will return true if the can.isMember function returns true.
• Otherwise, the value is not the correct type.

2. Handle values of another type

If the value is not the correct type:

• type.maybe and type.check will throw an error.
• type.convert and type.maybeConvert will convert the value using convert.