Closed ludeeus closed 5 years ago
So my opinion is that it should follow the structure for custom components and if thatโs a breaking change so be it... I assume itโs not possible for both approaches to coexist? Probably whatever you do youโre going to upset someone. It seems that eventually this change will be forced anyway? If so Iโd prefer to have my pain now.... Thanks for the explanation anyway. Iโm good with whatever you decide even though Iโd like to get rid of the warning.
I don't see a reason for this to be forced, but I have been wrong before. There can certainly be more than one "styles" of this, but I will only support one, and that is this one. Or the upcoming HACS if I ever get the time to finish that.
I think it will be better if everyone will aline with the recommended style. Chaos usually not a good thing.
So I guess folks really like breaking changes ๐คทโโ๏ธ Will get started on that when some time free up, probably not until Sunday/Monday (UTC)
We like order :)
Hahahahaha!!!! No ambiguity there is there. Lol.
Honestly, whatever keeps this component going I will do. I can't imagine life without it.
_Spin-off from https://github.com/custom-components/custom_updater/issues/131_
Issue:
This component is just a single file directly in the
custom_components
dir. To comply with recent changes this would need to change into something like blueprintAdd your vote as a reaction to this:
๐ Change the structure of this component (This WILL be a breaking change.) ๐ Leave it, it's just a warning. ๐ No opinion.
I'll leave this open until Sunday and will do the action based of the result then.