Congratulations on your previous work. Hopefully by now both of you have had some context about flight booking flow in general.
Traveloka has 2 kinds of booking flow:
In the standardized flow, we have the ability to add more products to the booking more easily because building blocks of which has been made generic by the package team–so product teams can just define their component and be done*. Few products, including flight, have been rocking the standardized flow for a while, and users should have already seen a more consistent look & feel when shopping in traveloka.
There are also a few differences in both general & technical perspective between standardized and non-standardized. Take a look at desktop flight booking, for example, which has adopted the standardized flow. You will notice there is in fact an additional step before we enter the actual booking form. This step is called pre-booking step, in which our customers can review their flight selection, add additional product(s) to their booking (airport transport, for instance), and review the total (search) fare–we'll learn about fare differences later.
On the technical side, differences are mainly on APIs & how we try to dynamically render form inputs based on given schema called View Description.
Today, we will learn about standardized booking flow & View Description! This knowledge hopefully helps us when migrating our non-standardized booking flow on mweb to the standardized one.
YOUR TASK:
src/shared/viewdesc/*
Good luck & happy hacking!
Note:
*while this looks simple & easy in theory, in reality they're not! So brace yourself :)