Skip to content

Fix duplicate OpenAPI path definitions - #3264

Open
anushka11p wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
anushka11p:fix-devtrack
Open

Fix duplicate OpenAPI path definitions#3264
anushka11p wants to merge 1 commit into
Priyanshu-byte-coder:mainfrom
anushka11p:fix-devtrack

Conversation

@anushka11p

Copy link
Copy Markdown

Summary

Fixes the API documentation page by removing duplicate path definitions from public/openapi.yaml. The OpenAPI specification now parses successfully and renders correctly in Swagger UI.

Closes #3263


Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that changes existing behavior)
  • 📝 Documentation update
  • ♻️ Refactor / code cleanup (no functional change)
  • ⚡ Performance improvement
  • 🔒 Security fix
  • 🧪 Tests only

What Changed

  • Removed duplicate /api/public/{username} mapping from public/openapi.yaml.
  • Removed duplicate /api/streak/freeze mapping from public/openapi.yaml.
  • Verified that the OpenAPI 3.1 specification parses without duplicate-key errors.

How to Test

  1. npm install
  2. npm run dev

Expected result:

The API documentation page renders successfully without YAML parsing errors, and /api/public/{username} and /api/streak/freeze each appear only once.

Screenshots / Recordings

| Before | After |
before:-

image

After:-

image

Checklist

  • Linked the related issue above
  • Self-reviewed my own diff
  • No unnecessary console.log, debug code, or commented-out blocks
  • npm run lint passes locally
  • No TypeScript errors (npm run type-check)
  • Added or updated tests where applicable
  • Updated documentation / comments if behavior changed

Accessibility (UI changes only)

image
  • Keyboard navigation works correctly
  • Color contrast meets WCAG AA standard
  • ARIA labels / roles added where needed
  • Tested on mobile / responsive layout

Additional Context

@github-actions github-actions Bot added gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix labels Jul 28, 2026
@github-actions

Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution type:bug GSSoC type bonus: bug fix

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: API Docs page fails to render (YAML parse error)

1 participant