We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is this a feature or a bug?
This could potentially be a bug too
Please describe the actual behavior.
I'm re-exporting a type from another module with module augmentation.
import * as rtdb from '@firebase/database-types'; // Augment the FirebaseDatabase type declare module '@firebase/database-types' { export interface FirebaseDatabase { getRules(): Promise<string>; getRulesJSON(): Promise<object>; setRules(source: string | Buffer | object): Promise<void>; } } // Re-export the augmented type export namespace database { export import Database = rtdb.FirebaseDatabase; }
The generated API reports (both the json file and the markdown file) do not mention any of the APIs added via augmentation.
What is the expected behavior?
APIs added via module augmentation should be included in the API report.
If this is a bug, please provide the tool version, Node.js version, and OS.
Potentially related: #2145, #1709
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is this a feature or a bug?
This could potentially be a bug too
Please describe the actual behavior.
I'm re-exporting a type from another module with module augmentation.
The generated API reports (both the json file and the markdown file) do not mention any of the APIs added via augmentation.
What is the expected behavior?
APIs added via module augmentation should be included in the API report.
If this is a bug, please provide the tool version, Node.js version, and OS.
Potentially related: #2145, #1709
The text was updated successfully, but these errors were encountered: