gavin/maybe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 28 Wiki Activity

Transaction rules engine V1 #1900

Merged
zachgoll merged 61 commits from zachgoll/rules-engine-v1 into main 2025-04-18 23:39:58 +08:00
Conversation 0 Commits 61 Files Changed 152 +4502 -612
zachgoll commented 2025-02-26 00:39:21 +08:00 (Migrated from github.com)
Copy Link

This PR introduces a basic rules engine that allows users to define "triggers" and "actions" that Maybe will automatically detect and apply to transactions during the "Sync" process:

CleanShot 2025-02-25 at 11 13 01

Initial scope

While a Rule may eventually apply to several models, this PR is a minimal implementation that focuses on:

  • Transaction records
  • Active/inactive rules
  • Effective dates
  • Basic AND/OR trigger condition logic
  • Categorization and tagging rules based on:
    • Text matching
    • Transaction values

Further rule templates will be added in the future, but these represent the highest impact rules for most users.

Self hosted vs. Hosted

Both versions of the app will have rules, but the hosted version will have additional controls that allow users to assign rules based on Plaid (data provider) info in addition to basic text/account/type matching.

This PR introduces a basic rules engine that allows users to define "triggers" and "actions" that Maybe will automatically detect and apply to transactions during the "Sync" process: ![CleanShot 2025-02-25 at 11 13 01](https://github.com/user-attachments/assets/05e040a6-8616-4caa-b2ac-20f0562eb332) **Initial scope** While a `Rule` may _eventually_ apply to several models, this PR is a minimal implementation that focuses on: - `Transaction` records - Active/inactive rules - Effective dates - Basic AND/OR trigger condition logic - Categorization and tagging rules based on: - Text matching - Transaction values Further rule templates will be added in the future, but these represent the highest impact rules for _most_ users. **Self hosted vs. Hosted** Both versions of the app will have rules, but the hosted version will have additional controls that allow users to assign rules based on Plaid (data provider) info in addition to basic text/account/type matching.
❤️ 14
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
📆 Planned
Not ready to be worked on yet, but planned for future
 💻 Self Hosted only
Issues pertaining to self-hosted versions of Maybe
 ⚙️ Config
ℹ️ Needs info
Further information is requested
 📱 Mobile
Bugs exclusively happening on mobile devices
 1️⃣ High Priority
High priority issues will be worked on next
 🚨 Urgent
Issues that are urgent for app functionality
 3️⃣ Low priority
Contributions accepted, but Maybe team will not be working on this in the near term
 2️⃣ Medium Priority
Community contributions accepted, Maybe team only works on if there are no high priority items open
 ⚡ Performance
Performance issues to address
 🎨 UI / UX
Issues related to UI / UX interactions and design.
 💎 Bounty
💰 Rewarded
📊 Data issue
Issues where the app functionally works, but the data is missing or inaccurate.
 🙋 Bounty claim
$1.5K
Community
This is a great issue for community members to work on
 dependencies
Pull requests that update a dependency file
 Design
Hosted only
Hosted app only
 Required self hoster data migration
Self hosters must run data migrations to resolve this issue
 ruby
Pull requests that update Ruby code
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gavin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gavin/maybe#1900
Delete Branch "zachgoll/rules-engine-v1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?