Set default for hass_config_yaml
fixture to ""
#88608
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
The
hass_config_yaml
fixture parametrizeshass_config_yaml_files
andmock_hass_config_yaml
.mock_hass_config_yaml
mocksconfiguration.yaml
or, whenhass_config_yaml_files
is set, multiple files.The current default of
None
forhass_config_yaml
is not very useful.This PT will change the default of
hass_config_yaml
to "".When
hass_config_yaml
orhass_config_yaml_files
are not set,mock_hass_config_yaml
will mock an emptyconfiguration.yaml
.Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: