Feat: Reconfiguration config flow #178
Annotations
2 errors and 4 warnings
Hassfest validation
[TRANSLATIONS] Invalid strings.json: extra keys not allowed @ data['config']['step']['user']['reconfigure_confirm']. Got {'title': 'Nordpool Sensor', 'description': 'Reconfigure Nordpool sensor', 'data': {'region': 'Region', 'currency': 'Currency', 'VAT': 'Include VAT', 'precision': 'Decimal rounding precision', 'low_price_cutoff': 'Low price percentage', 'price_in_cents': 'Price in cents', 'price_type': 'Energy scale', 'additional_costs': 'Template for additional costs'}}
|
Hassfest validation
Process completed with exit code 1.
|
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.
|
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.
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Loading