This repository was archived by the owner on Jul 27, 2025. It is now read-only.
Transaction rules engine V1 #1900
Merged
Conversation
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
zachgoll
force-pushed
the
zachgoll/rules-engine-v1
branch
from
8d1eb3f to
3bc0c18
Compare
This reverts commit 83dcbd9.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
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:
Initial scope
While a
Rulemay eventually apply to several models, this PR is a minimal implementation that focuses on:TransactionrecordsFurther 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.