Please enable JavaScript.

Coggle requires JavaScript to display documents.

Service repository, Affiliate, What for the week? (appetite setting) …

- - - - Tree model (recursive depth)
        
        Dynamic depth problem: https://github.com/prisma/prisma/issues/4562
        
        Materialized path
        
        prisma-extension-bark
        
        If not prisma, or bark -- is prisma extension required?
        
        POC
        
        Closure table
        
        GraphQL generated queries problem
        
        Nested set
        
        Adjacency list
      - General best practice: SQL
      - Existing approach
        
        Nodejs: typeorm (tree entities)
        
        PHP: laravel-trees
    - - Commission calculation
- - - - Winbox referral mechanism (player affiliate / decentralized affiliate / anyone can be affiliate)
      - Thai documentation (operator affiliate)
      - Other demo (consult aaron for links)
        
        what are crucial fields, what can be edited, etc --> put this on db schema design and endpoints
- - - - Lago deployment
        
        Info on vultr
      - Service logic / actual
      - Nest.js dynamic module
    - - Engineering design
        
        Service logic / pseudo
        
        Any new schema
        
        Webhook from/to?
      - Product design
        
        Billing period / mechanism?
        
        Any UI/UX in backoffice?
        
        Automation service setup, email sending, etc
        
        Operational workflow
    - - Unable to receive payment
        
        No billing system
        
        Rate not defined in db
    - - Lago deployment is 90% done in Vultr
    - - Understand charging metrics
        
        Royalty
        
        royalty based fee.. Negative GGR will be billed $0 zerorised
        
        Carry forward (pay next month)
      - Finalize charging model with stakeholders
  - - - Endpoints not designed
        
        Service logic unclear (service repo)
      - Infra not supported
        
        Endpoint cannot be protected
        
        API key not ready and authz approach not firm
- - - - New issue? Able to fix it once for all? Good time to fix now?
    - - Cannot resolve workspace
        
        Root problems
        
        Release workflow not determined/aligned
        
        Temporary can manual trigger
      - Games not loading
- - - - YD implemented without Actual Wireframe reference
        
        What do we want? Requirements unclear
        
        Prepare draft and have sync meeting
        
        Approach
        
        Out of scope
        
        Review the current outcome
      - API is not integrated
        
        API not planned/design
  - - - [Tomorrow] Review in vercel
      - Definition of Done
        
        Updated UI
        
        Header metadata reflected (ie Title, desc)
        
        Sharing links in social tested
- - - - Reset DB -> Seed
      - restart & seed with 3 workspaces, each with 3~5 players where u can easily switch profile
      - you can easily add or minus money or switch currency profile
        or switch [dev] currentCredential
      - you can easily see the money history (live updated)
      - to choose game provider > category > game and launch
      - to trigger sync (pull games by selecting specific game provider)
      - some potential benefit
        
        easy debugging
        
        repurpose as "testing portal" like AWC
        
        checkpoints for junior QA (to see wrong calculation issues, connection issues, negative balance issues, etc)
- - - - integration code actually google_spreadsheet mappers
      - run local scripts to process images, or upload images to s3 directly
- - - - Cater multi-factor username
      - Ready for mobile app
      - Cater API SDK
    - - Requirement: WebAuthn fingerprint
      - Requirement: Flexible username/phone
      - Requirement: Machine-to-machine API key
      - Personal API key
    - - Comparison and align choice
- - - - How to prevent flashing, etc
      - What to store in api / cdn / etc
      - How to design themeable components in future/guideline