Repository navigation
0.12.16
Pre-release
Pre-release
0.12.16
Bug Fixes
- Rule persistence (fire-and-forget) — All four rule management operations (add, toggle, reorder, remove) were discarding their async futures, so
notifyListenerscould fire before the write toSharedPreferencescompleted. Each operation nowawaits persistence before notifying listeners. - Invalid DSL silently accepted — Parse errors on rule save were swallowed. Errors now propagate to the VM, which sets a
saveErrorstate; the add/edit dialog stays open and shows the error message inline rather than saving a broken rule. - Remove default rule was a no-op — Removing a built-in default rule had no effect. Default rules are now hidden rather than deleted (stored under a
hidden_rule_nameskey). A "N hidden rules" section appears at the bottom of the list with individual Restore buttons. - Reorder only applied to user rules — Drag-to-reorder operated on the user rules list only, making it impossible to interleave user and default rules. Ordering is now driven by an explicit
rule_orderlist (stored under arule_orderkey) that spans both user and default rules. - No rollback on persistence failure — If a write to
SharedPreferencesfailed, the in-memory state was already mutated with no way to recover. All four mutation methods now snapshot state before mutating and restore the snapshot on failure. - New default rules invisible to returning users — Default rules added in a new app version would not appear for users who already had a saved rule order.
init()now appends any default rule entries absent from the saved order, so new built-in rules surface automatically on upgrade. - Snackbar spam on save error — A save error snackbar could re-fire on every unrelated
notifyListeners()call whilesaveErrorwas set. A_lastShownErrorguard now prevents duplicate snackbars.
Features
- New rules inserted at top of list — Newly added user rules appear at the top of the rules list rather than the bottom.
- User rule indicator — User-defined rules now display a star icon (amber) to distinguish them from built-in default rules.