NgDocPage
Page configuration interface, that should be used to describe configuration of the page
- Extends
NgDocBaseEntity
export interface NgDocPage extends NgDocBaseEntity { … }Members
Properties13 | |
category?: | The page category |
data?: unknown | Any custom data that you can provide for the page and use on it via |
demos?: Record<string, any> | undefined | The page demo components should be on object where key it's the component's class name and value it's class constructor |
disableFullscreenRoutes?: boolean | undefined | By default, a child route of a page opens as a standalone page: only the routed component, on the canvas of demos, with a link back to the page, without the navbar, the sidebar or the page. Set disableFullscreenRoutes to true to handle them yourself with a |
imports?: (readonly any[] | | Import Angular dependencies for the page. If you are using standalone components for demos and playgrounds, you don't need to import anything. |
mdFile: string | string[] | Path to the page markdown file |
onlyForTags?: string[] | undefined | Build tags this page is rendered for. The page is part of a build only when the build has at least one of these tags; otherwise it has no route, navigation item, search entry or keyword, as if it did not exist. A page without With the new generator engine (the Vite plugin, the
|
order?: number | undefined | Order is using for sorting entities in the sidebar |
playgrounds?: Record<string, | The page playgrounds should be on object where key it's the playground's name and value its playground configuration |
providers?: | List of providers for the page they will be available for all components on the page |
route?: string | | The route of the entity (current sourceFileFolder name by default) |
title: string | The entity title |