Des and Frontend notes

frontend_notes.md

Des tasks

Pending PRs

• [Theme] Add is_swappable helpers #7625 - Pending merge
• [Theme] Return retention_strategies via json - On hold for API-first approach
• [WIP][Checklist] He's making a list and checking it twice - Not scheduled, personal project

---

One time product

On theme engine

• PR: [Theme Engine OTP support #7331] (https://github.com/SocalProofit/customcheckout/pull/7331) - Done (deployed)
• Needs to pass through QA
• Apply changes to Legacy theme (they're on Base only)
• One-time/recurring pricing update to Base and Legacy theme
  • TP: [Theme] Show Discounted Price on Base Theme
  • TP: [Theme] Show Discounted Price on Legacy Theme

On old portal

• Bug in onetime product listed channel. Slack link
• TP: [OTP] Allow Non-Subscription OTP to be added to existing subscription

---

In QA

• Steve to test out One-Time product
• Make sure Steve has ability to test Theme Engine PRs on Heroku
• Give him access to Heroku
  • Squad-based Heroku
  • Get Deploy with Heroku on CircleCI working (alex)
• Was given an overview on the theme engine
• Get him set up with deploying a dev app

---

Theme engine

Templates

• Add One-Time layout updates to Legacy theme

Update routes

• Showing discounted price legacy themes add to one-time product branch?
• Check with Nikola on spreadsheet comparing objects
  • Spreadsheet: API vs Theme Engine objects
  • Needs JSON Object sample data
    • We have Theme Engine sample JSON in the GitHub wiki for Theme Engine
    • We have API sample JSON in the API docs
  • Write out strategy and TP issues

---

[ShopPort] Subscription Manager Mobile First

Broken up in to stories and ordered in suggested approach

• Decide on grid system (steal from our app)

• Render theme engine without proxy (Derek)

• Connect with George

  Where we're at:

  • George will not provide a desktop theme
  • For certain things, like Skip, do we do seperate pagers for secondary or tertiary actions or modals
  • Kayla will figure out design
  • We have screenshots stolen from George's design

---

Customer portal authentication

• Never on Des's plate

---

Theme engine (specific)

Updating routes

Nikola has a spreadsheet of routes that differ between API and Theme Engine

Spreadsheet: API vs Theme Engine endpoints

Tasks for Nikola

1. Add any routes still missing from the spreadsheet
2. Additional ways of labeling the routes:
   • Which route needs can be renamed?
     • These are "work-around" routes
     • Example: the API uses /charge/skip, but Theme Engine uses /subscription/skip
   • Which routes need to be built in the API?
     • If the feature doesn't exist.
     • Example: API doesn't allow product swapping
   • Is the route used by the existing Customer Portal?
     • Is this something old customer portal can currently do?
     • Example: We don't let customers delete orders or clone them, so no.
3. Take the new information in the spreadsheet and present to Mike to review
4. JSON samples of Theme Engine vs API
   • Use references from Wiki Docs (theme engine) and API docs (API)