backend: add coverage for platform link features (POST/PUT/DELETE /me/links)

[ShantKhatri]

Summary

Add small test coverage for create/update/delete platform link routes in apps/backend/src/routes/profiles.ts.

Tasks

• create tests verifying POST /api/profiles/me/links fails with invalid body and succeeds with valid body calling createLinkSchema.
• add test for PUT /api/profiles/me/links/:id when link not found returns 404.
• add test for DELETE /api/profiles/me/links/:id when existing link deletion returns 204.

Acceptance Criteria

• total 3+ test cases added and passing.
• this covers safeParse validation and typed responses.

[Aditya-K69]

I would like to work on this issue

[Dipti45sktech]

Hi @ShantKhatri . I'm interested in working on this, kindly assign it to me.

[ShantKhatri]

Hi @ShantKhatri . I'm interested in working on this, kindly assign it to me.

We already have one good-first issue in you bucket. Suggesting to start with feature or non-good-first.

[SMishra-27]

Hi @ShantKhatri , I’d like to work on this issue.

I’ll add test coverage for:

• POST /api/profiles/me/links
• PUT /api/profiles/me/links/:id
• DELETE /api/profiles/me/links/:id

including validation, success, and not-found scenarios while following the existing testing patterns in the repository.

[decodejatin]

Hi! I'd like to work on this issue.

I've reviewed the codebase and understand that this involves adding test coverage for the platform link management endpoints in
profiles.ts
. Based on the acceptance criteria, I plan to implement the following test cases:

POST /api/profiles/me/links

Test invalid request body (missing required fields, invalid platform, malformed data) to verify createLinkSchema validation
Test successful link creation with valid body, ensuring proper response structure and database persistence
PUT /api/profiles/me/links/:id

Test updating a non-existent link returns 404
Test successful update with valid data (bonus: could also verify ownership validation)
DELETE /api/profiles/me/links/:id

Test deleting an existing link returns 204
Test deleting a non-existent link returns 404 (bonus: ensures consistency with PUT behavior)
I'll follow the existing test patterns in the codebase and ensure all tests verify both the validation layer (safeParse) and typed responses.

Let me know if you'd like me to adjust the scope or if there are any specific edge cases you'd like covered!

[Shikhar-404exe]

Hi ,

I reviewed this issue and the related files. I have experience in this field of work.

I’d like to work on this issue and can start immediately. My plan is to:

• reproduce the issue locally
• trace the affected components
• implement and test the fix carefully

Please assign this issue to me if it's available.
Thank you!

[Aaryan1005194]

Hi @ShantKhatri, I’d like to work on this issue.

I’ve been working with backend APIs and test coverage in TypeScript-based projects, and this issue looks like a good opportunity to improve route reliability and validation handling.

I can add the required test cases for:

• POST /api/profiles/me/links validation and success scenarios
• PUT /api/profiles/me/links/:id returning 404 when the link does not exist
• DELETE /api/profiles/me/links/:id returning 204 for successful deletion

I’ll make sure the tests properly cover safeParse validation behavior, typed responses, and edge cases while keeping them aligned with the project’s existing testing structure.

Would love to contribute to this issue if it’s available.
Please consider assigning it to me and marking it under GSSoC’26.

[udaycodespace]

Hi @ShantKhatri, as per the Discord guidelines, sharing my approach before claiming this.

I've written route-level test coverage before in my college projects so I know the flow. Wanting to level up with a real open source codebase now.

Plan:

• POST: one case where createLinkSchema.safeParse fails (400), one where it passes and hits the handler (201)
• PUT /:id: mock DB returning null, assert 404
• DELETE /:id: mock existing record, assert 204

Will follow existing test patterns in the repo, nothing outside the test file.

ETA: tonight.

Can you assign this under GSSoC '26?