AFB want to use mch + mcp modules. Challenges: MCH is tightly coupled with @traveloka/core, while MCP has product-specific form integration. Might be easier to build their own from scratch
FVD itself is already uplifted from www to @traveloka/fvd. Can be used as needed.
UNS is hosted in the same traveloka/fvd-monorepo, it might be possible to create generic mch abstraction there. Will have another sync between infra, AFB, and william
RNW 13 broke range slider, still ongoing investigation. Will be worked by Kenny & Ferzos
It's fine to use logger module in client side (even though it's written in CommonJS)
logger.debug will be removed entirely from prod build, so it's safe to write a lot of log with this function
non warning logger will not be visible by normal user, you can call __logger__.setMinimalLevel in browser console to override
to send datadog from client, there's already existing function, will be shared by payment team
Some flaky tests are fixed, but some aren't: payment mobile confirmation, flight datepicker, and platform review submission image. Need help from product team to investigate these tests
Findings to reduce test flakiness has been compiled to slide deck https://docs.google.com/presentation/d/15gykCcxAdz6nrDuSSdNbc0RzIrSSfoGbQwyrCYUmHbI/edit#slide=id.p. Feel free to share to product engineers
RNW v14 will be worked on next month by Kenny

MoM 2021-02-11