Skip to content

Update config flow

Update config flow #4

Triggered via push August 14, 2024 13:51
Status Failure
Total duration 1m 37s
Billable time 2m
Artifacts

hassfest.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 2 warnings
validate
[SERVICES] Service add_booking has no name and is not in the translations file
validate
[SERVICES] Service add_booking has no description and is not in the translations file
validate
[SERVICES] Service add_booking has a field bookingReference with no name and is not in the translations file
validate
[SERVICES] Service add_booking has a field bookingReference with no description and is not in the translations file
validate
[SERVICES] Service add_booking has a field dateOfbirth with no name and is not in the translations file
validate
[SERVICES] Service add_booking has a field dateOfbirth with no description and is not in the translations file
validate
[SERVICES] Service add_booking has a field surname with no name and is not in the translations file
validate
[SERVICES] Service add_booking has a field surname with no description and is not in the translations file
validate
Process completed with exit code 1.
validate
[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.
validate
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/