Closed grahambrown11 closed 1 year ago
Yes. I've already lost a battle against the speaker thing.
The docs ara added to the json by another script which is in the docs repo.
I might just push an schema update for the non conflicting components meanwhile.
Thanks for giving it a try!
So I fiddled and manually pulled out just the new component I created https://github.com/esphome/dashboard/pull/496 would be nice if this could be handled by an automated GitHub Action routine...
@glmnet I am happy to remove the base SPEAKER_SCHEMA as its really not needed? It can be added back later if something gets added into the common schema
I was looking at it. Actually the oddity here is that the schema is empty, I didn't understand first hand why it was different.
Let's keep it this way as it makes sense.
I'll wait for this month release and push a full schema update.
Thank you
Close with #80
@glmnet the "newish" speaker component breaks the build scheme script: https://github.com/esphome/esphome/blob/17fed954bf74a018f527b541dab2d30101169bb8/script/build_language_schema.py#L533 My quick fix was to add
But don't think that's a solution 😜, I am trying to get the new alarm_control_panel component to get the auto complete suggestions in the dashboard.
The VSCode script refers to
build_jsonschema.py
which seems to be replaced bybuild_language_schema.py
but that is missing the#!
& the execute flag so it doesn't run 😞All the
"docs"
attributes are removed after runningbuild_language_schema.py