Have a Pinned Repaired List For Next Release Update So No Duplicated Repair Requests In The Open Issues

[comet424]

ive seen this before you get in trouble for reporting an Open issue when its Open and not repaired yet you gotta look in the Closed Articles and guess if something has been fixed but not really fixed till a new update...

it be nice a Pinned Article under Open Issues To Read like
Bug Fixes In Next Update Please Read Before Making Open Issue
and under it be like

Fixes To Be Released In Spook V3.1.1
Detected that custom integration 'spook' accessed lovelace_data['dashboards'] instead of lovelace_data.dashboards

this way no one will have to get in trouble to read anything it be there that its been fixed and we just need to wait for it to be released in the following update least no one will get confused or anything

[frenck]

Welcome to GitHub.

If you have suggestions for them, I would suggest reporting it to them.

Also, see the list item in the FAQ of the documentation: https://spook.boo/faq

../Frenck