UNPKG

@angular/material

Version:
46 lines (45 loc) 2.1 kB
{ "$schema": "http://json-schema.org/draft-07/schema", "$id": "SchematicsMaterialM3Theme", "title": "Material 3 Theme Schema", "type": "object", "properties": { "primaryColor": { "type": "string", "description": "Color for primary color palette", "x-prompt": "What HEX color should be used to generate the M3 theme? It will represent your primary color palette. (ex. #ffffff)" }, "secondaryColor": { "type": "string", "description": "Color for secondary color palette", "x-prompt": "What HEX color should be used represent the secondary color palette? (Leave blank to use generated colors from Material)" }, "tertiaryColor": { "type": "string", "description": "Color for tertiary color palette", "x-prompt": "What HEX color should be used represent the tertiary color palette? (Leave blank to use generated colors from Material)" }, "neutralColor": { "type": "string", "description": "Color for neutral color palette", "x-prompt": "What HEX color should be used represent the neutral color palette? (Leave blank to use generated colors from Material)" }, "directory": { "type": "string", "description": "Workspace-relative path to a directory where generated theme file will be created", "x-prompt": "What is the directory you want to place the generated theme file in? (Enter the relative path such as 'src/app/styles/' or leave blank to generate at your project root)" }, "useSystemVariables": { "type": "boolean", "default": false, "description": "Whether to use system-level variables for the theme.", "x-prompt": "Do you want to use system-level variables in the theme? System-level variables make dynamic theming easier through CSS custom properties, but increase the bundle size." }, "themeTypes": { "type": "string", "enum": ["light", "dark", "both"], "description": "The components to migrate.", "x-prompt": "Choose light, dark, or both to generate the corresponding themes" } } }