-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define TypeScript schema for responses #685
Comments
I haven't seen a type scheme defined without an actual library. Might be interesting to see an existing case. |
I'm thinking of something like: Where the types are delivered independently of the actual library. I guess then also specref itself would also use them - though it's not really a library in the traditional sense. |
That corresponds to the actual library named |
BTW I think getting a JSON schema file would probably be better for multiple language support 👀 |
Like these? |
Oh cool. Maybe use things like https://www.npmjs.com/package/json-schema-to-typescript to generate TypeScript lib then? |
It be nice to have a TypeScript types file, for APIs that consume this.
(I've not had a chance to do something like this before, but would be useful for projects like ReSpec that consume this data)
CC'ing @saschanaz who may provide guidance? 🙏
I think what we need is described in:
https://www.typescriptlang.org/docs/handbook/declaration-files/templates/module-d-ts.html
The text was updated successfully, but these errors were encountered: