angular-cn/aio/content/examples/component-styles/stackblitz.json

{
  "description": "Component Styles",
  "files": [
    "!**/*.d.ts",
    "!**/*.js",
    "!**/*.native.*",
    "!**/*.[1].*"
  ],
  "file": "src/app/hero-app.component.ts",
  "tags": ["CSS"]
}
feat(aio): copy example code from angular.io 2017-02-22 13:13:21 -05:00			`{`
			`"description": "Component Styles",`
			`"files": [`
			`"!*/.d.ts",`
			`"!*/.js",`
docs: Component Styles guide for CLI (#19791) 2017-11-03 14:12:34 -04:00			`"!*/.native.*",`
			`"!*/.[1].*"`
feat(aio): copy example code from angular.io 2017-02-22 13:13:21 -05:00			`],`
build(docs-infra): always specify a landing file for StackBlitz projects (#34553) The StackBlitz API (which we use to generate StackBlitz projects on the fly, when a user clicks on a live example link in the docs) allows specifying the file to open in the editor by passing a query param. If no file is specified, StackBlitz opens a default one. In the past, it used to be `main.ts` and nowadays it seems to be `app.component.ts`. StackBlitz builder, the tool that we use to generate the StackBlitz projects, allows specifying the primary file by setting the `file` property in the corresponding `stackblitz.json`. Previously, if the `file` property was not set, StackBlitz builder would not specify a file, thus falling back on StackBlitz's default behavior. This was not great, because the default behavior may change unexpectedly is the future to something that is less useful for our users. This commit change StackBlitz builder to always specify a primary file. If no file is specified in `stackblitz.json`, the builder will look for the first file that exists in the example from a list of predefined files. Partially addresses #22357. PR Close #34553 2019-12-23 22:29:59 -05:00			`"file": "src/app/hero-app.component.ts",`
feat(aio): copy example code from angular.io 2017-02-22 13:13:21 -05:00			`"tags": ["CSS"]`
			`}`