hyperweb-io / hyperweb-io/ts-codegen

move away from json-schema-to-typescript

Open
#7 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
126
Forks
31
Avg merge
19m
Merged PRs (30d)
2

Description

Currently we're depending on `json-schema-to-typescript`, however, it's limited (as noted here https://github.com/pyramation/cosmwasm-typescript-gen/issues/10) so we should look into fully parsing/processing types internally

examples to inspire

https://github.com/iamssen/cosmwasm-typescript-generator/blob/main/cosmwasm-typescript-generator/src/transform/createTypeStore.ts

https://github.com/bcherny/json-schema-to-typescript/blob/master/src/typesOfSchema.ts

https://github.com/bcherny/json-schema-to-typescript/blob/master/src/types/JSONSchema.ts

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no repository files, tests, or entry points. Start by reviewing the current json-schema-to-typescript integration, then compare the referenced createTypeStore.ts, typesOfSchema.ts, and JSONSchema.ts examples. Done should mean the project fully parses and processes types internally without that dependency, but the issue does not define the exact scope or validation criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.