dev-create-service

Generating an API data layer requires a base API URL and a sample response shape to automate creation of types, contracts, adapters, and services. It scaffolds distinct files like [resource].types.ts and [resource]-adapter.ts for separation of concerns.

Separating API contracts from data fetching involves mapping inbound snake_case payloads to camelCase app contracts in pure adapters, while services handle native fetch calls exclusively. This architecture prevents data transformation logic inside fetching blocks.

The generated service layer uses native fetch without try/catch blocks to ensure deterministic API calls. It excludes data transformations entirely, relying on pure adapters to implement side-effect-free mappings between API payloads and app models.

Mapping snake_case API payloads to camelCase app contracts is handled by pure adapter files like [resource]-adapter.ts. These adapters implement side-effect-free inbound and outbound transformations between the API and app models.

You do not need try/catch blocks in the generated service because the architecture explicitly omits them to maintain deterministic fetch execution. All data mapping and side-effect handling is pushed entirely to pure adapter files.

You can use this to scaffold types and adapters for frontend-backend communication by generating API-aligned types in [resource].types.ts and pure adapters in [resource]-adapter.ts. This conforms to separation of concerns architecture guidelines.