Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Manual Account Creation, Create Transaction Behavior, and Documentation Updates #64

Merged
merged 8 commits into from
Jan 9, 2024

Conversation

CalvinChanCan
Copy link
Contributor

This PR adds the following changes:

  • feat: Introduces create_manual_account and get_account_type_options to facilitate the creation of a new manual account within MonarchMoney.

    • create_manual_account allows users to create a manual account with specific attributes.
    • get_account_type_options provides available account types and their subtypes for reference during account creation.
  • feat: Updated the behavior of create_transaction. Previously, new transactions would automatically update the account's balance. But a recent change in MonarchMoney added a update_balance field which defaults to false. This updates create_transcation to use the new field whether the transaction should update the account balance or not.

  • docs: fixed spelling and added new methods

Copy link
Owner

@hammem hammem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question inline, but I think this would be fine as is.

FYI, @grablair , this addition will make the unit testing easier.

Comment on lines +292 to +293
"type": account_type,
"subtype": account_sub_type,
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if these are invalid? Should the code pull the types implicitly and check them for folks?

@hammem hammem merged commit 1240127 into hammem:main Jan 9, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants