So this might be a good time to refactor the component to accept a single post prop instead: Vue. Defining a prop for each related piece of information could become very annoying: So far, we’ve only registered components globally, using Vue.component: Vue.component( 'my-component-name', Īs our component grows, it’s likely we’ll not only need the title and content of a post, but also the published date, comments, and more. There are two types of component registration: global and local. To use these components in templates, they must be registered so that Vue knows about them. For the latest districtwide updates, please read our weekly Family Digest or visit. It’s common for an app to be organized into a tree of nested components:įor example, you might have components for a header, sidebar, and content area, each typically containing other components for navigation links, blog posts, etc. ParentVUE ParentVUE Resources Known Issues Login or activate by clicking 'Activate Account'.
0 kommentar(er)
