-
Notifications
You must be signed in to change notification settings - Fork 705
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
Empty type declarations #524
Comments
I suspect that it is due to missing support of /**
* Database connection configuration data structure for a single
* environment.
*/
export interface DbEnvConfig {
[name: string]: string;
url: string;
dialect: string;
} |
Probably related but I get similar behavior for this: putDelegates(data: { a: string, b: string, c: string[], d?: string }, callback?: cback<any>): Promise<any> {
} The generated doc shows "data" as "object" not providing any hint on the allowed elements. I could create an interface but I've hundreds of methods with different inputs. Wouldn't really be a use case for interfaces. |
@vekexasia I think that is a separate issue. Per #497 it should be giving some basic info by default. If you want more details you should use an interface. |
Hey! Bumping the issue :) |
#1103 should fix this. |
Imaging I have the following type declaration
As result I get this representation in generated documentation:
If I will add indexes to type:
I would see this:
So I missing all the properties defined for a type. For me it looks like a critical bug (I dunno if is suggested to be expected behavior). In such a case documentation itself loses its meaning, as the most critical information is missing from it. Better to look on the source code then...
The text was updated successfully, but these errors were encountered: