Validate #129
validate.yml
on: schedule
Hassfest Validation
1m 13s
HACS Validation
23s
Annotations
9 errors and 2 warnings
HACS Validation
<Validation topics> failed: The repository has no valid topics (More info: https://hacs.xyz/docs/publish/include#check-repository )
|
HACS Validation
<Integration dotKrad/hass_bring_shopping_list_component> 1/7 checks failed
|
Hassfest Validation
[MANIFEST] Manifest keys are not sorted correctly: domain, name, then alphabetical order
|
Hassfest Validation
[SERVICES] Service install has no name and is not in the translations file
|
Hassfest Validation
[SERVICES] Service install has a field repository with no name and is not in the translations file
|
Hassfest Validation
[SERVICES] Service register has no name and is not in the translations file
|
Hassfest Validation
[SERVICES] Service register has a field repository with no name and is not in the translations file
|
Hassfest Validation
[SERVICES] Service register has a field repository_type with no name and is not in the translations file
|
Hassfest Validation
Process completed with exit code 1.
|
Hassfest Validation
[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.
|
Hassfest Validation
[TRANSLATIONS] config.title key has been moved out of config and into the root of strings.json. Starting Home Assistant 0.109 you only need to define this key in the root if the title needs to be different than the name of your integration in the manifest.
|