Skip to main content

Frontend Onboarding

This track is for developers working mainly in intt-portal.

Your main repo​

  • intt-portal

What frontend developers usually do​

Current team workflow for frontend work is simpler than the full platform setup:

  • clone only intt-portal
  • run the portal against staging-backed APIs
  • use staging Swagger docs to inspect available endpoints
  • develop on a feature branch
  • merge through development
  • deploy or promote toward staging
  • let QA validate on the staging site

What to install​

  • Node.js
  • pnpm
  • optional global Angular CLI

Files to check first​

  • intt-portal/.env
  • intt-portal/src/environments/environment.staging.ts
  • intt-portal/src/proxy.conf.json

Main local commands​

Install:

cd /path/to/INTT/intt-portal
pnpm install

Run with staging-backed data:

pnpm run start:stg

Alternative:

ng serve --configuration=staging

Test:

pnpm run test

Minimum backend to start​

For normal frontend work, the team does not usually run backend services locally.

Instead, frontend developers use staging-backed APIs exposed through Swagger and the staging site.

Staging Swagger references​

Use these to discover and test endpoints:

  • https://intt-stg.tm.com.my/ticket/docs#/
  • https://intt-stg.tm.com.my/setting/docs#/
  • https://intt-stg.tm.com.my/data/docs#/
  • https://intt-stg.tm.com.my/auth/docs#/

QA validation target​

QA can validate frontend changes on:

  • https://intt-stg.tm.com.my/

Branch flow​

Current frontend branch path:

<feature-branch> -> development -> staging

Common frontend tasks​

  • update Angular pages and services
  • trace API base URL chosen by environment config
  • inspect auth callback flow
  • verify module routes and guards
  • inspect or confirm endpoint shapes from staging Swagger

Common frontend gotchas​

  • using pnpm run start instead of pnpm run start:stg
  • missing .env keys for crypto or staging auth
  • assuming you need every backend repo locally for normal frontend work
  • assuming all modules use the same backend service