Skip to content

Conversation

dcapslock
Copy link
Collaborator

Replaces PR #1004

@dcapslock dcapslock marked this pull request as ready for review September 30, 2025 02:10
@dcapslock
Copy link
Collaborator Author

Note: We can't call this disabled as trying to template that just breaks such a config. Users would be able to set disabled, like visibility, but we don't need to document that.

@dcapslock
Copy link
Collaborator Author

dcapslock commented Sep 30, 2025

Frontend listens to card-visibility-changed and if card itself has hidden HTMLElement property set then will set style, disconnect and then reconnect again later on next card-visibility-changed event when hidden is not longer set.

@RomRider
Copy link
Collaborator

It means we can template the hidden property. But this would be "on top" of visibility's core config I guess?

@dcapslock
Copy link
Collaborator Author

Yes. The benefit is tempting.

@RomRider RomRider changed the title feat: Support templates for hidden to hide the card completely feat: Support templates for hidden to hide the card completely Oct 16, 2025
@RomRider RomRider merged commit 263d366 into custom-cards:dev Oct 16, 2025
3 checks passed
github-actions bot pushed a commit that referenced this pull request Oct 16, 2025
## [5.1.0-dev.4](v5.1.0-dev.3...v5.1.0-dev.4) (2025-10-16)

### Features

* Support templates for `hidden` to hide the card completely ([#1013](#1013)) ([263d366](263d366)), closes [#1004](#1004)

### Bug Fixes

* custom_fields cards are not recreated from scratch anymore if their config is modified ([#1064](#1064)) ([2d8aaa4](2d8aaa4)), closes [#1060](#1060)
Copy link

🎉 This PR is included in version 5.1.0-dev.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants