-
Notifications
You must be signed in to change notification settings - Fork 38
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
DO NOT MERGE: POC using json-schema-to-typescript library #702
base: main
Are you sure you want to change the base?
Conversation
5856707
to
a4b9cdf
Compare
@@ -0,0 +1,162 @@ | |||
export type Metadata = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These file souldn't be checked in, but doing so for folks to review and see output
@@ -0,0 +1,6 @@ | |||
/** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The library seems to have a bug whereby just defs alone in a file will not generate any definitions. It will generate definitions via a schema which is why core.d.ts has flow definition generated.
export type Metadata = { | ||
[k: string]: unknown; | ||
}[]; | ||
export type Metadata1 = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should MetaData be a general concept which is leveraged by flow.json and core.json to prevent this
This PR contains the early proof-of-concept (PoC) work with model generation #701
Lessons learned will be attached to issue rather than PR.