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

Feature Request: Support multiple YNAB budgets #645

Open
whatuserever opened this issue Feb 9, 2025 · 1 comment · May be fixed by #647
Open

Feature Request: Support multiple YNAB budgets #645

whatuserever opened this issue Feb 9, 2025 · 1 comment · May be fixed by #647
Labels
enhancement New feature or request

Comments

@whatuserever
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I'm using YNAB with multiple budgets, and I'm unable to choose which account should be mapped to which budget. They all have to be mapped to the same budget.

Describe the solution you'd like
In the YNAB config, change the layout such that the budget is defined per account:

Account number Ynab budget id Ynab account id
<accountNumber> <ynabBudgetId> <ynabAccountId>

Describe alternatives you've considered
None

Additional context
I'm willing to work on this :)

@whatuserever whatuserever added the enhancement New feature or request label Feb 9, 2025
@whatuserever
Copy link
Contributor Author

I started looking into this and I'm not sure if it's possible to make this change without breaking existing configs.

Saving the budget per account would require changing the YnabConfig type.
Any suggestions on how to keep backward compatibility?


Sidenote, why is the same type defined on 3 files? backend/commonTypes.ts, preload/commonTypes.ts, and renderer/types.ts.

@whatuserever whatuserever linked a pull request Feb 10, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant