fix: re-evaluate transactions when a category rule is deleted#89
Open
MarkIannucci wants to merge 1 commit into
Open
fix: re-evaluate transactions when a category rule is deleted#89MarkIannucci wants to merge 1 commit into
MarkIannucci wants to merge 1 commit into
Conversation
deleteCategoryRule previously only removed the row, leaving transactions with categories assigned by the deleted rule until the next save/sync. It now runs applyAll() like saveCategoryRule, so affected transactions fall back to a lower-priority rule or revert to Uncategorized. The TUI and GUI surface the recategorized count. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
Tested locally, LGTM. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
deleteCategoryRule previously only removed the row, leaving transactions with categories assigned by the deleted rule until the next save/sync. It now runs applyAll() like saveCategoryRule, so affected transactions fall back to a lower-priority rule or revert to Uncategorized. The TUI and GUI surface the recategorized count.