We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
beta missing documentation missing doc comments
With an export like this:
/** * Returns true if fn returns true for every item in the iterator * * Returns true if the iterator is empty * * ## Example * ```typescript * all(e => e > 1, [1, 2, 3]) // false * all(e => e > 0, [1, 2, 3]) // true * all(e => e > 1, []) // true * ``` */ export const all: { <T>(fn: (item: T) => boolean, iterator: IterableOrIterator<T>): boolean <T>(fn: (item: T) => boolean): (iterator: IterableOrIterator<T>) => boolean } = curry2(function all<T>( fn: (item: T) => boolean, iterator: IterableOrIterator<T>, ): boolean { for (const item of asIterable(iterator)) { if (!fn(item)) { return false } } return true })
typedoc should generate documentation that includes both the two signatures as well as the written documentation with the example.
typedoc only generates documentation for the two signatures but the written documentation is missing.
The text was updated successfully, but these errors were encountered:
Fixed in beta 29 - this was a tricky one...
Sorry, something went wrong.
fix: Missing comments on variable functions
e15bcd6
Closes #1421
I tested version 0.20.0-beta.31 now. It works great. Thank you!
No branches or pull requests
Search terms
beta
missing documentation
missing doc comments
Expected Behavior
With an export like this:
typedoc should generate documentation that includes both the two signatures as well as the written documentation with the example.
Actual Behavior
typedoc only generates documentation for the two signatures but the written documentation is missing.
Steps to reproduce the bug
Environment
The text was updated successfully, but these errors were encountered: