Release v3.6.0 · nutteloost/todo-swipe-card

ToDo Swipe Card v3.6.0

Now requires Home Assistant 2026.4 or newer. This release switches to Home Assistant's new WebAwesome-based UI components (ha-input, ha-dialog-footer). If you are still on Home Assistant 2026.3 or older, please stay on v3.5.2.

Font size in the editor: Two new fields in the visual editor's Display Options let you set the text size without writing any YAML. Font size controls the todo item text (and the add-item field, descriptions and due dates); Title font size controls a list's title text. (closes #23)
UIX Support: Todo Swipe Card now applies UIX styling directly, so it works on both the swipe card itself (top-level uix:) and on individual lists (per-list uix:). (closes #27)

Items due tomorrow no longer slip past hide_future_items: With this option turned on, items due in the future are meant to stay hidden — but depending on your timezone, some items due tomorrow could still show up. They are now reliably hidden, so you only see items due today or earlier. (closes #21)
Dialog buttons restored: After Home Assistant's 2026.3 dialog migration the Save, Cancel and Delete buttons vanished from the edit-item dialog and both delete-confirmation dialogs. Buttons are now placed in the new ha-dialog-footer so they appear and work again. (closes #22)
Edit dialog header & task-name field restored: Home Assistant 2026.5 removed ha-textfield, which left the dialog title and the "Task name" field blank. Both now render correctly via the new ha-input component and header-title. (closes #22)
Card editor fields restored: Every text field in the visual editor (Card Spacing, Title Text, Background Image URL, Custom Icon, Maximum items) was blank on recent Home Assistant versions and now works again. (closes #22)
Display Order dropdown restored: The per-list "Display Order" selector in the editor now uses the updated ha-select API, so all sort options appear and can be selected. (closes #22)

Thanks to @LokiLuciferase and @micium for diagnosing the breakage and contributing the initial fix (PR #24). Thanks to @tjuuljensen (PR #26).