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
Missing array types #196
Comments
@jeffpyke thanks for filing an issue! Yes that’s something being worked on for a You can preview an alpha build now with The short version is that 1.0 tried to be “too smart” and abstract too much, but it results in errors like you’re seeing. 2.0 is a rewrite that is “dumber” in the sense that it perfectly mirrors your schema (and the library itself is also easier to maintain). You can follow progress on the roadmap. Hopefully it’ll be released soon! Also, if you find that the |
Thanks @DangoDev , I tried that and saw this error.
Please let me know if this is a known issue. If not I can provide a more detailed bug repro. |
Hm. I’m actually surprised you’re seeing that on the |
It's working now (I see next was updated, nice!) Thanks! |
By the way, is there a way to remove the "definitions" namespace? e.g.
becomes
preferred:
|
Good question! You can actually change the name with type aliasing. E.g. import { definitions } from './my-schema';
export type MyObject = definitions; Or import { definitions as MyObject } from './my-schema'; Or you can even combine schemas if you have to manage multiple: import { definitions as schema1 } from './schema1';
import { definitions as schema2 } from './schema2';
export interface MyObject {
schema1: schema1;
schema2: schema2;
} |
(I know this is a repeat message and you’ve already been pinged for this; I’m just repeating for archival purposes, for people that search closed issues) |
Some types are missing in Typescript output.
Example swagger 2.0 input:
Output:
The FloatArray definition is missing.
The text was updated successfully, but these errors were encountered: