[Backend Refactor] Extract reusable public response transformers for profile and card routes

[SMishra-27]

Summary

The apps/backend/src/routes/public.ts route handlers currently contain repeated inline response transformation logic for public profile, card, and link-related payloads.

Several route handlers manually construct response objects with similar transformation patterns, including:

• public profile formatting
• card response shaping
• public link transformation and serialization

This duplication increases maintenance overhead and makes future schema or response updates more difficult to manage consistently across the backend.

---

Proposed Refactor

Introduce reusable transformer/helper utilities for constructing public response payloads instead of repeating inline object mapping logic across route handlers.

Potential extraction targets include:

• public profile response transformation
• public card response formatting
• link serialization/transformation logic

The goal is to centralize response shaping behavior while preserving the existing API contract and route behavior.

---

Expected Benefits

• Reduce duplicated backend transformation logic
• Improve maintainability and readability
• Standardize response formatting across public routes
• Simplify future schema and response updates
• Improve long-term scalability of route handlers

---

Scope

Primary target:

apps/backend/src/routes/public.ts

Additional helper utilities may be introduced if necessary, while keeping the refactor minimal, isolated, and fully backward compatible.

---

Acceptance Criteria

• Repeated inline response mapping logic is reduced
• Existing API responses remain unchanged
• Refactor remains fully backward compatible
• Route readability and maintainability are improved
• No unrelated backend functionality is modified

---

Notes

This issue focuses strictly on backend refactoring and maintainability improvements without introducing new features or changing API behavior.

[SMishra-27]

@Harxhit , please assign this issue to me

[VIDYANKSHINI]

Hi @Harxhit,

I’d like to work on this backend refactor issue.

My approach would be to extract the repeated response transformation logic from apps/backend/src/routes/public.ts into reusable helper/transformer utilities while keeping the existing API contract fully intact.

Planned refactor includes:

• extracting reusable transformers for public profile responses
• centralizing card response formatting logic
• creating shared helpers for public link serialization/transformation
• reducing repeated inline mapping logic across route handlers
• keeping the refactor isolated and backward compatible
• ensuring response structures remain unchanged for existing consumers
• improving readability and maintainability of the route layer

I’ll also make sure the extracted utilities are cleanly organized and reusable for future public route expansions without affecting unrelated backend functionality.

Please assign this issue to me if it’s available. Thanks!

[Harxhit]

@SMishra-27 I have assigned this issue to you.

[Pcmhacker-piro]

Hi @Harxhit,

I’m interested in contributing to this project and would love to work on this issue. I have experience working on open-source contributions and would be happy to implement the required changes.

Could you please assign this issue to me? Thanks!