rogelio-o / economify Goto Github PK

In the issuer update page, add a button to create a category rule (issuer type) directly.

In a new transaction to be added, if the issuer is null or the category is null, try to find a transaction with the same concept (with a lookup by distance, with more than the x%) and copy the attributes from this transaction.

To bear in mind: the new attribute which locks the category should be also copied.

A button in transactions to trigger the recategorization of all the transactions.

A first approach will call a backend service which will iterate over all the transactions and it will categorize them. A most sophisticated solution would be add each transaction to a queue that will be processed with the pace the system can support. The second solution would need a frontend page or component in which the user could see the progress of the categorization (and recategorization) and it could be also use when a transaction is created.

The category_id should be added to the path (/categories/:category_id/rules) and then used for: creating new rules, updating new rules (the rule has to match with the rule ID and category ID), getting rule by ID (same that before), viewing rules pages (filtering rules by category ID) and deleting rule (like updating case).

Adding back button next to the collapse menu button to go back to the previous page. It should not have the same behaviour than the go back button of the browser, but the one we consider. For example: if we are on the update page after a insertion, go back will go to the list page and not to the creation page.

We could add a property to the Page component to indicate the previous page. If there is no previous page, the button will not be rendered.

An issuer could have different names in different transactions. Because these transactions are issued by the same issuer, we need a way to make possible that an issuer has different names.
Adding a new field to the issuers with alias could be a solution. This field should be an array of different alias (or a comma separated string with them).

A checkbox to lock the category of a transaction should be added in order to avoid change the category in a recategorization. The checkbox should be checked automatically when the user change the category of the transaction manually.

Obviously, in the backend, this new attribute should be added to the transactions table and the recategorization service should be modify to exclude this transactions for being recategorized.