Please enable JavaScript.
Coggle requires JavaScript to display documents.
Reggie Client, Reggie Next - Coggle Diagram
Reggie Client
App
Before Mount
-
-
-
-
-
-
-
-
if addItem query string does not exists, add the default flow product to cart
-
sets user token in redux store after fetching it from auth call or if it exists in localStorage already
if sld query string exists, fetches the domain and auto adds to cart if it's available
if addItem query string exists
- fetches it along w/ any promotional code and/or
brand_flow flag
- if fetched product does not exist in cart adds fetched product to cart w/ specified term (Note: if fetched product is hosting and
onlyOneHosting flow extra flag exists, remove existing hosting in cart first)
- if
brand_flow query string alters with localStorage, then replace existing similar cart product w/ url product
- if an url product matches a similar product in the cart (i.e., product of same group), then remove the existing cart product and add the new url product in cart
-
-
-
-
After Mount
if user gets redirected from paypal or billdesk, we need to handle redirect by retrieving query strings from the url and update store based on data provided
if products in cart, call order summary after mount
we need to make a followup order summary call in case when tax exists and there is tax exemption or VAT number is available in redux store
-
if currency of any cart product differs from currency in cookie, then re-add cart products w/ proper currency from cookie
-
-
-
-
call window events - resize, reggie.setFields
-
-
-
-
-
-
-
New Approaches
We no longer want to be in charge of UI whatsoever. We only provide HOCs that serve global states and actions calls that FoS can leverage however the way they want. Pros:
- Give unlimited freedom and flexibility to FoS to render whatever and however they want for their brand specific needs. We just provide data and common core functionalities
Cons:
- Possibly increase the work that FoS need to do for a new or existing components since we will no longer going to be doing things behind the scenes automatically for them.
We provide a clear API for all of our HOCs, global states and actions for FoS to use. We also provide code examples for FoS to reference and use
Components
Error
-
NOTE: there are duplicates errors scattered across errors actions, we need to clean it up
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Reggie Next
-
Domain Search Management
-
-
-
Validate potential invalid TLDs before search (i.e., if TLD is totally random and not in registry OR if TLD is simply not compatible with a brand)
We need to format domain product to indicate whether it's transferable domain, associate domain, addable domain or unavailable domain
Helpers like isTransferDomain(), isAssociateDomain, isAddableDomain, isUnavailableDomain() would be great for CAP and/or external teams to make use of perhaps
-
Product Management
-
Create product groups to display different addons based on
different conditions (i.e., customer interactions with cart, hosting specific products, based on products in cart and so on)
-
-
-
-