Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve explanation of configuration validation #14000

Merged
merged 2 commits into from
Oct 5, 2022

Conversation

emontnemery
Copy link
Collaborator

@emontnemery emontnemery commented Oct 5, 2022

Proposed change

Improve explanation of configuration validation:
image

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example configuration

Additional information

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

bramkragten
bramkragten previously approved these changes Oct 5, 2022
"heading": "Configuration validation",
"introduction": "Validate your configuration if you recently made some changes to it and want to make sure that it is all valid.",
"heading": "Restart",
"introduction": "A basic validation of the configuration is automatically done before restarting. The basic validation ensures the YAML configuration doesn't have errors which will prevent Home Assistant or any integration from starting. It's also possible to only do the basic validation check without restarting.",
"check_config": "Check configuration",
"valid": "Configuration valid!",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we change this to Configuration will not prevent Home Assistant from starting! 😝

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I gotta say I don't like this change. It's very wordy and I think people might think something is wrong instead of it saying valid/ok/good etc.

IMO the failure case should be the longer one and explain where a person should go to fix the problem.

@bramkragten bramkragten merged commit 83a4fd6 into dev Oct 5, 2022
@bramkragten bramkragten deleted the improve_configuration_check_translation branch October 5, 2022 10:12
@github-actions github-actions bot locked and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants