GIT HUB ISSUES
Is your feature request related to a problem? Please describe.
The issue with the budget and debt feature is that they are functioning independently. The goal is to link both of the features so that values from the budget can be used in the debt feature. However, due to the lack of a functioning database, this feature has been difficult to implement.
Describe the solution you'd like
For the feature to work smoothly, having a working database is a good place to start. In this case, you can have a schema that interacts with the database to to fetch data from the budget feature to the debt feature. For example, a query to fetch total savings from the budget feature and use it as money available in the debt feature.
Describe alternatives you've considered
I ran into issues while trying to link total savings from the budget feature to the debt feature. I tried using props, but due to the logic already established in the project, there were a lot of bugs. If you choose to go down this route, I suggest having a concrete knowledge of the backend and a solid grasp on props. Additionally, I tried implementing an SQLite database, but due to the structure of the back end, I ran out of time while imposing it. Choosing this route will conflict with the solid pod database that has already been used in the backend. Therefore, getting the solid pod working might be the best option.
Additional context
In the screenshots below, the money available in the debt feature should be $2500 instead of $5000. The $2500 is from the total savings in the budget feature screen shot below.
Budget feature
Debt feature
GIT HUB ISSUES
Is your feature request related to a problem? Please describe.
The issue with the budget and debt feature is that they are functioning independently. The goal is to link both of the features so that values from the budget can be used in the debt feature. However, due to the lack of a functioning database, this feature has been difficult to implement.
Describe the solution you'd like
For the feature to work smoothly, having a working database is a good place to start. In this case, you can have a schema that interacts with the database to to fetch data from the budget feature to the debt feature. For example, a query to fetch total savings from the budget feature and use it as money available in the debt feature.
Describe alternatives you've considered
I ran into issues while trying to link total savings from the budget feature to the debt feature. I tried using props, but due to the logic already established in the project, there were a lot of bugs. If you choose to go down this route, I suggest having a concrete knowledge of the backend and a solid grasp on props. Additionally, I tried implementing an SQLite database, but due to the structure of the back end, I ran out of time while imposing it. Choosing this route will conflict with the solid pod database that has already been used in the backend. Therefore, getting the solid pod working might be the best option.
Additional context
In the screenshots below, the money available in the debt feature should be $2500 instead of $5000. The $2500 is from the total savings in the budget feature screen shot below.
Budget feature
Debt feature