#hass.data[DOMAIN]

1 messages · Page 1 of 1 (latest)

steady skiff
#

With regards to https://github.com/home-assistant/core/pull/168760, do we want to migrate legacy apps (that do not have a config flow) to HassKey?
cc @solemn topaz

I migrated to runtime_data based on a search of hass.data[DOMAIN][entry.entry_id] or hass.data[DOMAIN][config_entry.entry_id]

#

I was planning a second pass to look at all the remaining uses of hass.data[DOMAIN] and a lot of them are just very old legacy integrations that do not use config flow so I wanted to know if the idea is to:

  • migrate them to HassKey
  • or add an ignore flag (because legacy)
solemn topaz
#

Legacy should be upgraded to Bronze imho

#

I'm going to exclude them btw. I've now used it to create an epic with taks for all existing violations