NEARBuilders / NEARBuilders/everything-dev

orpc-v2: UI client and everything-dev type-gen on v2 types

Open
#266 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ready-for-agent
Dominant language
TypeScript
Stars
5
Forks
6
Avg merge
1m
Merged PRs (30d)
1

Description

Ticket ID: B6

Parent

#248 — orpc-v2: consolidate fork into everything-dev and migrate platform to oRPC v2 + Effect 4 (epic)

What to build

Stage B, step 6: move the UI's api client and the everything-dev CLI's generated contract types onto v2 type names — ContractRouterClientRouterContractClient and AnyContractRouterRouterContract — in both the type-generation module and the child-repo scaffold templates. Regenerate the gitignored generated types (bos types gen) and confirm the auto-regen hooks (typecheck / bos dev / bos build) still work.

Acceptance criteria

  • UI typecheck green against regenerated v2 types
  • Child-repo scaffold templates emit the new type names; bos init output compiles
  • bos types gen round-trips; auto-regen on typecheck/dev/build intact

Blocked by

  • #260 — migrate all six contracts to the v2 route builder
  • #265 — host handlers, OpenAPI 3.1.1 pin, and MCP tool generation

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the type-generation module and child-repo scaffold templates, then inspect the bos types gen command and the typecheck, bos dev, and bos build auto-regen hooks. Confirm the v2 names are emitted throughout, regenerated types pass UI typecheck, bos init output compiles, and generation round-trips. This work is blocked by issues #260 and #265.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, cli, frontend, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.