Our current purchase flow is the following:
- Create order
- Add accommodation item 1
- Add accommodation item 2...
- Finalize order
- Do payments
*Set a range* | |
hotel:{ID}:room{ID}:{YEAR}:{DAY} range {RANGE} avail {AVAILABILITY} | |
172.26.0.2:6379> hmset hotel:100:room:2:2017:1 range 31 availability 5 | |
OK | |
*Get a range* |
#!/bin/bash | |
#projects=( proxy svc-offer svc-reservation www-le-admin www-le-customer svc-voucher) | |
projects=( proxy svc-offer svc-reservation www-le-admin www-le-customer) | |
commands=( start dev start start dev "run hot") | |
count=0 | |
for i in "${projects[@]}" | |
do | |
terminator --new-tab -e "cd ~/Projects/${i} && yarn ${commands[${count}]}" |
APP_ENV=local node migrate.js | |
//migrate.js | |
require("dotenv-safe").config({ | |
path: ".env" | |
}); | |
const config = require("../src/config").get(); |
damon+t1309@genoapay.com | |
damon+aucu123@genoapay.com | |
Password1 | |
Test Card Details: | |
Card number: 4111111111111111 | |
Expiry date: date in the future: eg 12/19 | |
CSV: 111 | |
For the surcharge you use the surcharge value that is returned from the calendar endpoint.
{
"status":200,
"message":null,
"result":{
LEs current approach is to combine rooms by rate ids so that we can display standard rates and package rates in the same option tile.
We've noticed that for some searches the same rooms rate id is differen't between standard rates and package rates.
We get rate: 1234 with package: false
We get rate: 1234 with package: true
But sometimes in the response the same rates for a room come back with differen't id so we are unable to combine them.