Skip to content

v0.1.1 — Performance & correctness fixes

Choose a tag to compare

View all tags
@rusty4444 rusty4444 released this 17 May 06:43
v0.1.1
8cd2b4e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

First HACS update release. Pulls in the performance and correctness fixes from #7 (closes #1–#6).

Highlights

  • Template fetch dedupe + in-memory cache. Multiple linked cards on a page no longer issue duplicate GET /linked_cards/templates/<id> requests — concurrent lookups share one in-flight promise, and results are cached until a template is saved or deleted.
  • Single-template REST endpoint. New GET /linked_cards/templates/<id> so each card only fetches what it needs instead of the full template list. The list endpoint still exists for the manager UI.
  • Idempotent setConfig. Re-applying the same config (Lovelace edit save, dashboard refresh, etc.) is a no-op — no child rebuild, no flicker.
  • Child card reuse. As long as the rendered child config is unchanged, the existing child element is kept and only its hass is updated. Avoids tearing down sub-cards on every state update.
  • Stable getCardSize. Returns the last measured child size when the child briefly can't report one, instead of falling back to a default mid-render and causing layout jank.
  • Render-race guard. A monotonic render token ensures a slow async render cannot overwrite a newer one.

Backward compatible: existing dashboard YAML, the list endpoint, and the linked-card-manager editor are unchanged.

Upgrading via HACS

  1. Open HACS → Frontend (or Integrations) and look for Linked Cards.
  2. Click Update to pull 0.1.1.
  3. Restart Home Assistant if HACS prompts you.
  4. Hard-refresh your dashboard (Ctrl/Cmd+Shift+R) so browsers drop the cached linked-card.js.

No template migration is required.

Source

Assets 2
Loading