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
Currently, we have the InsertEntryUseCase, but we don't have ways for users to insert (add) an entry.
Design
After clicking the "Add Entry" button, we may want to open a dialog for users to fill in the information of the newly added entry.
After filling in the information and clicking the "Confirm" button, we may need to validate the information to make sure they are in the correct format.
Then, the InsertEntryController is called.
After all, the BillUpdateController should be called to update the screen to display the newly added entry.
Details
If we are adding a splitter entry, then we need a way to inherit the information from the parent normal entry. This may be solved by implementing some enhancements in the use case layer.
Initiations
InsertEntryUseCase
, but we don't have ways for users to insert (add) an entry.Design
InsertEntryController
is called.BillUpdateController
should be called to update the screen to display the newly added entry.Details
TODOs
InsertEntry
andBillUpdate
use cases. #70The text was updated successfully, but these errors were encountered: