You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing from ynab4 or ynab web, there are no category rules created after import. Typically rules are only created when categories are manually set by the user. (Or brought in from an acutal import).
I think having them for the ynab importers would be an improvement, as the outcome would likely more closely match the ynab experience they were having with auto-categorisation.
Describe your ideal solution to this problem
Expose the already existing learnCategories up through addTransaction and the api so importers can make use of it
Turn on learnCategories for the importers
Teaching and learning
API changes should be documented in the API reference, but I don't think there is existing references that have boolean flags like this that have default values.
The text was updated successfully, but these errors were encountered:
This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
When importing from ynab4 or ynab web, there are no category rules created after import. Typically rules are only created when categories are manually set by the user. (Or brought in from an acutal import).
I think having them for the ynab importers would be an improvement, as the outcome would likely more closely match the ynab experience they were having with auto-categorisation.
Describe your ideal solution to this problem
learnCategories
up through addTransaction and the api so importers can make use of itTeaching and learning
API changes should be documented in the API reference, but I don't think there is existing references that have boolean flags like this that have default values.
The text was updated successfully, but these errors were encountered: