Random idea while looking at our more

[naive cape]

Not the full list, maybe just a mention "BE carreful this entity is part of 62 automations, and 5 dashboards"
I like this approach, keeping the dialog simple and focused on the task.

[tired flicker]

I would have the code ready for the FE. For dashboard I need to add something to core to find the entity in related dashboards. Should we also mention the group and scene count?

[naive cape]

Oh yes! Good idea

[naive marsh]

Maybe some line breaks? I would definitely gloss over that way too easily

[timber vessel]

Here's what I'd absolutely LOVE for this:

Really delete foo_bar_baz?

This entity is used in 12 automations, 3 scripts and 1 dashboard.

[ See Related ]   [ Cancel ]  [ Delete ]

where See Related would take you to a filtered search so you can start cleaning up.

similarly, "1 dashboard" is often too ambiguous when you make heavy use of subviews. It usually takes a lot of Ctrl-F in raw YAML to track it down.

[naive cape]

I would simplify the sentence by dropping the are you sure part:

“This entity is used in 12 automations, 3 scripts and 1 dashboard.”

[naive cape]

Good idea! Downside is that it opens a dialog over de confirmation dialog. Would we have a way to do this better?

[naive marsh]

Dropdown?

Or make it similar to the restart bottom sheet. It also has a dropdown.

Or is it a drop-up? lol

[timber vessel]

in my version, the story would be “oh, I want to clean up before I delete it” so the See Related implies canceling the deletion

[naive marsh]

If I'm looking up an entity and go to delete (which involves a few steps already) I'd just want a quick glance what might break.

"Ah it's just that stuff let's go ahead" I wouldn't want to backtrack if it wasn't anything relevant

[merry idol]

What about this,

Delete [entity-name]

Deleting an entity is an irreversible action. Are you sure you want to continue?

This entity is associated with 1 automation, 1 script, 1 group and 1 dashboard.

Deleting an entity is permanent. Continuing may cause issues!

And if there aren't any associations:

Delete [entity-name]

Deleting an entity is an irreversible action. Are you sure you want to continue?

This entity is not associated to anything, and will therefore not cause any issues if deleted.

[naive cape]

We had the entity name in the tile before. We dropped that because sometimes the entity name is huge.

[merry idol]

That's fine, IMO

As long as most of the name is visible, you can just end up truncating it

The alternative is ...

[merry idol]

Maybe something like this then?

Delete Entity

Deleting [entity-name] is irreversible and permanent.

This entity is associated with:
1 automation
1 script
1 group
1 dashboard

Deleting this entity could affect your existing associations and cause them to break. Continue at your own risk.

[naive marsh]

I'll present you sensor.schlafzimmer_bewegungsmelder_beleuchtungsstarke

[naive cape]

Germans invented the printing press because they were tired of handwriting

[naive marsh]

It's my longest non gibberish entity id. Perfect for stress testing lol

[naive marsh]

I'd drop the "cause them to break" part or rewrite it. It sounds like you're deleting C:\System32

Otherwise it's a good idea i think to include more information given there are no tight space constraints

[merry idol]

I mean, there's definitely concern for things to break if you delete an entity :)

Better to make newbies worried about deleting an entity, than to allow them to delete it willy-nilly without checking

[naive marsh]

But what are people's expectations? I deleted my weather entity, oh why isn't my weather showing on my dashboard...

[tired flicker]

Well, based on my day to day job I can say, not everyone is expecting a deletion when they hit delete 🙈

[timber vessel]

again, this is highly story dependent, but stuff like:

"hm, I think this might be a dupe"
"I'm not using this"
"I'll clean this up before reinstalling"

...and similar reasons. knowing exactly what gets affected is either A) extra reassurance or B) a great way to avoid an "oh shit" moment

[sacred breach]

While not all of these listed are valid, there is a LOT of potential places an entity can be used. Gathering them all might be difficult, and showing just some of them isn't a full picture

[onyx marsh]

+1 to this suggestion from me, and if including the entity name in the dialog title is a concern, I would go for "are you sure" as the title and replace "this entity" by its name in the text.

I love the idea of allowing the user towards a filtered search right from here. For me, the dialog would close (I agree that it implies cancelling deletion) and opening / navigating to wherever the user can do their cleanup.

[naive cape]

"are you sure" as the title and replace "this entity" by its name in the text.
The title should explain the action, in this case delete. We shouldn't have any are you sure titles.

We can show the entity name in the description.

[onyx marsh]

Sorry, wasn't aware of such a guideline, but I agree, it's better to explain the action in the title 👍

[merry idol]

Delete Entity is the best way to describe it, really

[tired flicker]

So this is now what I've 🙂

[merry idol]

We need to name the entity in the delete, just in case the user isn't certain what is being deleted

[tired flicker]

Name or entity ID?

[naive cape]

Name

[merry idol]

yeah that's good. I'd personally emphasize the fact that deleting the entity whilst it's still connected to other things could cause things to break (because it can)

[merry idol]

And I'd put the name + each thing it's part of in bold, like here