core/homeassistant/components/onboarding/manifest.json

{
  "domain": "onboarding",
  "name": "Home Assistant Onboarding",
  "after_dependencies": ["hassio"],
  "codeowners": ["@home-assistant/core"],
  "dependencies": ["auth", "http", "person"],
  "documentation": "https://www.home-assistant.io/integrations/onboarding",
  "integration_type": "system",
  "quality_scale": "internal"
}
Add manifests (#22699) * Add manifests * Update auto name * Update codeowners * Add requirements from platforms * Minor cleanup * Incorporate changes from awarecan PR 2019-04-04 04:14:45 +00:00			`{`
			`"domain": "onboarding",`
Correct names in manifests (M-P) (#30541) 2020-01-07 12:28:35 +00:00			`"name": "Home Assistant Onboarding",`
Add support for IoT class in manifest (#46935) 2021-04-15 08:21:38 +00:00			`"after_dependencies": ["hassio"],`
			`"codeowners": ["@home-assistant/core"],`
Move analytics setup to later stage to avoid delaying frontend startup (#112535) Move analytics setup to stage 1 to avoid delaying frontend startup analytics was only needed in the frontend startup phase for onboarding. Its very unlikely the user will be able to complete the onboarding steps and get to the analytics screen before analytics is done loading so we can delay loading it until stage 1. To be absolutely sure that it is ready, the core_config step in onboarding will wait to proceed if it is some how still being setup 2024-03-07 01:37:41 +00:00			`"dependencies": ["auth", "http", "person"],`
Sort manifests 7 (#87028) 2023-02-08 19:32:43 +00:00			`"documentation": "https://www.home-assistant.io/integrations/onboarding",`
			`"integration_type": "system",`
			`"quality_scale": "internal"`
Add manifests (#22699) * Add manifests * Update auto name * Update codeowners * Add requirements from platforms * Minor cleanup * Incorporate changes from awarecan PR 2019-04-04 04:14:45 +00:00			`}`