[x] Migration to have default: 'pending' in db schema
Routes
[x] #edit route bookings/:id/edit
[x] #support route support with static troll page
Unavailable ship
[x] Book it now is changed to You can't book this ship
Status pending
[x] User can use Cancel action
[x] User can edit booking (and total amount must be re-calculated)
[x] Owner can use Decline or Accept action
Status validated
[x] User can edit but the status goes back to pending
[x] User can cancel but
[ ] Triggers penalties : 10% of the total owed to owner in a penalty_amount + can't book any ship until penalty_amount = 0
[ ] Sweet alert : Bounty hunters sent to fetch his ass just in case
[x] Owner can cancel without limitation.
Status paid
[x] User can cancel
[ ] Sweet alert : Don't you think you're gonna be refund!
[x] Owner can cancel and User is refund
[ ] Sweet alert : You won't keep that money no!
Status closed
[x] Owner can use Close action once date_end is passed and he has got back his ship. In other word, Close action available if today >= date_end and status is Paid.
[x] Once closed, ask an admin for any modifications with a button Ask admin
Tabs
[ ] 3 tabs : Incoming rides, My monkey business, Good ol' days
Background tasks
[ ] Status is pending after date_start : Auto-update to cancelled and cancellation attributed to owner. Increment cancel_quantity
[ ] Status is validated after date_start : Auto-update to cancelled and penalties triggered to user. Assign penalty_user_id & increment penalty_amount
Default status
Routes
Unavailable ship
Status pending
Status validated
[x] User can edit but the status goes back to pending
[x] User can cancel but
[x] Owner can cancel without limitation.
Status paid
Status closed
Tabs
Background tasks
cancel_quantitypenalty_user_id& incrementpenalty_amountPenalty mechanism
penalty_user_id:integer+penalty_amount:bigint+cancel_qty:integerCancellation hall of shame
cancel_qtyare performed by each owner and establish a top ten of the worst owners.Reviews