GitHub
Twitterprops
A static property used to create ObservableObject-like properties on each StacheElement instance.
static props = { ... };
To manage the logic and state of an element, ObservableObject-like property definitions can be added to explicitly configure how an element's properties are defined.
To add property definitions, add a static class field like shown below.
import { StacheElement } from "can/everything";
class TodoItem extends StacheElement {
static props = {
name: String,
completed: false
};
}
customElements.define("todo-item", TodoItem);
const todo = new TodoItem()
// `initialize` must be called for properties to be set up
.initialize({ name: "go grocery shopping" });
todo.name; // -> "go grocery shopping"
todo.completed; // -> false
Note: to see all the options supported by
define, see can-observable-object.
static get props() { return { ... }; }
For browsers that do not support class fields (and applications not using a transpiler), properties can be defined using a static getter like shown below.
class TodoItem extends StacheElement {
static props = {
name: String,
completed: false
};
}
customElements.define("todo-item", TodoItem);
Note: to see all the options supported by
define, see can-observable-object.
Use
Defining a property using a shorthand or definition object is a great way to encapsulate the logic and state of an element's properties.
Among other things, this can be used to create
- typed properties using type checking or type conversion
- declarative, derived properties
- required properties
These are discussed below and the full set of options can be found in the ObservableObject documentation.
Typed properties
Typed properties can be used to ensure that the value of an element's property is the expected type. Types are strict by default, but type conversion is also available for properties that do not need to be stricty typed through methods like type.maybe, type.convert, and others.
The following example...
import { StacheElement, type } from "can/everything";
class Person extends StacheElement {
static view = `
<p>{{first}}</p>
<p>{{last}}</p>
<p>{{age}}</p>
<p>{{birthday}}</p>
`;
static props = {
first: String,
last: type.maybe(String),
age: type.convert(Number),
birthday: type.maybeConvert(Date)
};
}
customElements.define("per-son", Person);
let fib = new Person({
first: "Fibonacci",
last: null,
age: "80",
birthday: undefined
});
document.body.appendChild(fib);
Declarative properties
Declarative properties can be used to create properties that functionally derive their value from other property values. There are many options for creating declarative properties, including getters, asynchronous properties, and even techniques similar to event streams and functional reactive programming.
The following example shows a few examples of declarative properties:
<per-son></per-son>
<script type="module">
import { StacheElement } from "can/everything";
class Person extends StacheElement {
static view = `
<p>First: <input value:bind="first"></p>
<p>Last: <input value:bind="last"></p>
<p>Full Name: {{fullName}}</p>
<p>Name Changes: {{nameChangeCount}}</p>
`;
static props = {
first: "Kevin",
last: "McCallister",
get fullName() {
return `${this.first} ${this.last}`;
},
nameChangeCount: {
value({ listenTo, resolve }) {
let count = resolve(0);
listenTo("fullName", () => {
count = resolve(count++);
});
}
}
};
}
customElements.define("per-son", Person);
</script>
Required properties
Required properties ensure that if an element is instantiated without a value for that property, an error will be thrown.
In the following example, an error is thrown because the <to-do> element is instantiated without a name property. To prevent this, the element should be created with a value for name like <to-do name:raw="Go Shopping" />.
<to-do></to-do>
<script type="module">
import { StacheElement } from "can/everything";
class Todo extends StacheElement {
static props = {
name: { type: String, required: true }
};
}
customElements.define("to-do", Todo);
</script>
For all of the options available for defining properties, see the ObservableObject documentation.