use createSelectSchema for api routes where applicable

Description

Contributor guide

Tech stack

typescript

Domain

apibackend

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

TypeScript knowledgeZod basicsProject API structure

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

First, review the related PR #263 to understand the attempted implementation and why it failed. This will provide context on the expected usage of createSelectSchema. Then, examine the API route definitions in the codebase (likely under src/routes/ or similar) to find routes that currently use other schema validation methods. Finally, evaluate which routes can benefit from using createSelectSchema based on the pattern established in PR #263, and discuss with maintainers for clarification on 'where applicable'.