Open ChrisBaker97 opened 11 months ago
Yup this may happen and is actually ok to ignore.
Essentially, this statement can be put everywhere. The extension has some logical places to shallow those, but setting them on every single parameter would not make sense either. So, this is a balance game without a solution at this point.
../Frenck
I suppose there's no easy way to borrow HA's code to actually assemble and parse those as if they were part of the configuration.yaml
file itself before linting it?
nope
Parsing
configuration.yaml
produces errors when template entities are included using!include_dir_named
:All works fine, and the configuration passes Home Assistant's YAML validation.
Please include the related YAML code:
A representative file,
template_sensors/illumination.yaml
:Extension runs in:
I'm running VS Code on:
I'm accessing my files: