Case:
Kot 1:
Beer Mug => 2 regular, 2 happy hour
Kot 2:
Beer Mug => 2 Regular
Kot 3:
Beer Mug => -2 Regular
Then move Kot 2 to new table would leave the voucher with 2 hh and 0 regular
Also, just move did not check if products were going negative.
Chore: Model relationships updated to make them simpler
Chore: Bill printing majorly refactored for it
Due to the sheer depth of the changes. There can be showstoppers. Please test it carefully
Moved to sqlalchemy 2.0
Added type checking as much as possible
Updated angular to 15
Moved from Angular flex layout to tailwind css
Started developing on vscode with devcontainers
Since the amount Behaviour Subject pipe was not being subscribed to
and the original Behaviour Subject as being subscribed,
amountVal was not being populated. Now it will be.
This was creating problem where amount in receive payment was always 0
Added a check in the backend so that if any part of bill remains unsettled, it will give an error instead of silently accepting and removing the entry.
The data is kept as the original bill object and this view generated on every change. It has no sanctity.
To deal with the challenges of Selection of items in the bill.component.html created a bill selection item.
This is converted to string while checking else the selection model fails.
Feature: It now checks if Happy Hour items have equivalent regular items in each kot.
Feature: Discount won't apply to happy hour items.
Checks for both are both in front end and back end.
Amritanshu Agrawal