[Vue.js3.0]Guide–ComponentsInDepth–Props

# Props

This page assumes you've already read the Components Basics. Read that first if you are new to components.

# Prop Types

So far, we've only seen props listed as an array of strings:

Usually though, you'll want every prop to be a specific type of value. In these cases, you can list props as an object, where the properties' names and values contain the prop names and types, respectively:

This not only documents your component, but will also warn users in the browser's Javascript console if they pass the wrong type. You'll learn much more about type checks and other prop validations further down this page.

# Passing Static or Dynamic Props

So far, you've seen props passed a static value, like in:

You've also seen props assigned dynamically with v-bind or its shortcut, the : character, such as in:

In the two examples above, we happen to pass string values, but any type of value can actually be passed to a prop.

# Passing a Number

# Passing a Boolean

# Passing an Array

# Passing an Object

# Passing the Properties of an Object

If you want to pass all the properties of an object as props, you can use v-bind without an argument (v-bind instead of :prop-name). For example, given a post object:

The following template:

Will be equivalent to:

# One-Way Data Flow

All props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. This prevents child components from accidentally mutating the parent's state, which can make your app's data flow harder to understand.

In addition, every time the parent component is updated, all props in the child component will be refreshed with the latest value. This means you should not attempt to mutate a prop inside a child component. If you do, Vue will warn you in the console.

There are usually two cases where it's tempting to mutate a prop:

1. 
   The prop is used to pass in an initial value; the child component wants to use it as a local data property afterwards. In this case, it's best to define a local data property that uses the prop as its initial value:

2. 
   The prop is passed in as a raw value that needs to be transformed. In this case, it's best to define a computed property using the prop's value:

# Prop Validation

Components can specify requirements for their props, such as the types you've already seen. If a requirement isn't met, Vue will warn you in the browser's Javascript console. This is especially useful when developing a component that's intended to be used by others.

To specify prop validations, you can provide an object with validation requirements to the value of props, instead of an array of strings. For example:

When prop validation fails, Vue will produce a console warning (if using the development build).

# Type Checks

The type can be one of the following native constructors:

• String


• Number


• Boolean


• Array


• Object


• Date


• Function


• Symbol

In addition, type can also be a custom constructor function and the assertion will be made with an instanceof check. For example, given the following constructor function exists:

You could use:

to validate that the value of the author prop was created with new Person.

# Prop Casing (camelCase vs kebab-case)

HTML attribute names are case-insensitive, so browsers will interpret any uppercase characters as lowercase. That means when you're using in-DOM templates, camelCased prop names need to use their kebab-cased (hyphen-delimited) equivalents:

Again, if you're using string templates, this limitation does not apply.