jcswanson / efinance Goto Github PK

• BankAccount Entity should work with the User Entity
• BankAccount should be an optional part of the HTML form that updates the User's account
• BankAccount will need to connect to the Loan Entity
• BankAccount will need to work in some kind of controller
• Make the User to Bank Account relationship be @OnetoOne
• Make the Loan to Bank Account be a @manytoone

The above is just to get you guys started but add new issues if you want to break this down

• Should contain a User to access the user information
  Don't worry about over complicating this because it is mainly being used for the BankAccount details and Payment feature. Maybe allow the user to change his username and basic details.
  Might need a DB Schema file added to the resources folder in order to share the DB setup in GitHub

• Get the Auto Loan functioning with a Controller
• Get the Personal Loan functioning with a Controller
• Get the Business Loan functioning with a Controller
• Loan Controllers must display a View named loan-accounts.html that contains a table of the different loans applied for by the current User

Use a Loan class that has the default instance variables common to all three loans used in the project. Then use inheritance to apply the Loan variables to the subclasses. The Loan class should contain a User.

• We need to Join a User in the Loan class which also joins in the database.
• The entity-relationship between the User and Loan could be One User to Many Loans OR Many Users to Many Loans? I'm still trying to understand this. Anyone can try to figure it out.
• Test a Loan Controller that returns a new Loan with User (Possibly a @RestController ?)