dnoulet/go-guess
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
go-guess/frontend/README.md
Daniel Noulet 6153017b62 review
2026-09-19 20:56:27 +02:00

3 KiB
Raw Blame History

Go Guess frontend

React and TypeScript recruitment workspace built with Vite.

Commands

npm install
npm run dev
npm run typecheck
npm run lint
npm run format
npm run format:check
npm test
npm run build

Run one test:

npm test -- src/App.test.tsx -t "shows answer inputs"

API integration

Vite proxies /api to http://localhost:8080. Login stores the returned JWT in sessionStorage; protected requests send it as Authorization: Bearer <token>. API failures are shown in the UI and are never replaced with demo data.

Supported routes:

  • POST /api/auth/login
  • GET|POST /api/jobs
  • GET /api/jobs/:id
  • PATCH /api/jobs/:id for interview status and duration
  • POST|DELETE /api/jobs/:id/questions/:questionId
  • GET /api/jobs/:id/candidates
  • GET|POST /api/jobs/:id/invitations
  • GET /api/jobs/:jobId/invitations/:invitationId for protected answer review
  • GET|POST /api/questions (GET accepts ?search=)
  • PUT /api/questions/:id to update question text, type, options, reference answer, and code snippet
  • PATCH /api/questions/:id to deprecate or restore a question
  • GET|POST /api/participants
  • GET /api/participants/:id
  • GET /api/participants/:id/photo
  • GET /api/participants/:id/cv
  • GET /api/interviews/:token
  • POST /api/interviews/:token/accept
  • PUT /api/interviews/:token/answers/:questionId
  • POST /api/interviews/:token/finish

Participant creation uses multipart fields firstName, lastName, birthday, email, contactInfo, photo, and cv.

Interview workflow

Authenticated interviewers create and edit reusable questions at /questions, configure job status and duration, attach active library questions, and generate invitations for each eligible participant from a job detail page. Multiple-choice and radio questions require at least two explicitly added options. Detaching a question removes only the job association; questions can be deprecated but not deleted. Open-answer and code-review questions include an interviewer-only reference answer that is never rendered in the participant interview. Code-review questions also require a code snippet. Accepted and completed invitations can be opened from the job to review every participant answer, possible choice options, reference answers, and code-review context; unanswered questions are called out explicitly.

Participants open the generated /participant/:invitationId URL without signing in. The opaque invitation ID authorizes the existing /api/interviews/:token API. Code-review questions are shown in a pull-request-style code panel with a review comment field. Answers are saved when navigating between questions and as they change, then Submit completes the interview. The countdown is derived from the backend acceptedAt timestamp plus the job duration so refreshing cannot reset it. Questions stay hidden until the participant explicitly accepts the invitation.

Container

Build with docker build -t go-guess-frontend .. The production Nginx server serves the SPA and proxies /api to the Docker Compose service api:8080.