FR: Mark non-existing entities

[andriej]

Lately I've ran in "let's clean up some things" mood and I've found out that my .yaml's contain a lot of non-existant (anymore) entities. Example? Recorder's include/exclude list of particular entities - some of them are like 30 versions of HA old.

Would be great feature to have those entities that does not exist in HA marked-down/underlined, so any further edit of files will not leave them behind.

[bieniu]

Yeah, such feature is missing a lot.

[keesschollaart81]

It's indeed an awesome idea I could use myself as well! Thanks! I'm not sure if I can/will build this in the next couple of weeks but I leave the issue open as I really want to have this and build it some time!

[phixion]

came here to request the same. I think .storage/core.{entity,device}_registry holds the relevant information

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[andriej]

I think it's still worth keeping open :-)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[andriej]

Still :-)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[andriej]

Still valid

[phixion]

@keesschollaart81 thank you

[ThomDietrich]

Is there any activity or update on this? Feels like one of the most relevant missing features for the otherwise great extension. Thanks

[frenck]

@ThomDietrich Nope! Feel free to contribute it.

[ThomDietrich]

JS/TypeScript is my weak spot 🙈 zero experience but Hey, just yet another programming language 😄

Would you be able to share how difficult this task might be and which risks you see? Would be useful for me and maybe for anyone else listening

[frenck]

Would you be able to share how difficult this task might be and which risks you see?

I am not able to judge that.

[kubawolanin]

I was looking at this issue and would like to help implementing this. Once we finalize #1880 to a mergeable form, it should be fairly easy to access entities on the extension level. It even might be a contribution point on the language server side (diagnostics?).

Implementation-wise: When onDocumentChange event is triggered, we'll need to iterate over all entity-like strings in the opened document, and then compare them with a list of available/subscribed entities. If a match is not included in the list, return a warning.

[ThomDietrich]

Hey Kuba, so delighted to see you again after all these years! Sounds like a plan 🚀 Thanks for #1880 which looks great and for considering the ticket here.

[kubawolanin]

I made some progress today 💪🏻