REFACTOR: Opposite transfer's transaction to reference original transfer transaction and vice versa.

Context

From #16

Adding a comment to this as there is no currently reliable solution to reference the opposite transaction generated by the transfer balance function.

We could do as @Harshvardhan1012's implementation before that is to use the transaction's id as the opposite transaction's transactionId and vice versa. This might require a refactor on the updateTransaction, deleteTransaction, and few other methods. So, I'm opening another issue about it.

Another issue that can be another feat issue is recurring transfers. This can be explored after the above aforementioned has been resolved.

Solution

We could do as @Harshvardhan1012's implementation before that is to use the transaction's id as the opposite transaction's transactionId and vice versa. This might require a refactor on the updateTransaction, deleteTransaction, and few other methods. So, I'm opening another issue about it.

Affected Functions

• updateTransaction
• deleteTransaction
• [ ]

Affected functions are incomplete. There could be more functions or ui elements affected.