Ian Sanders
Ian Sanders
The `Paths` section of the output file is structured like: - Paths - PathId - Parameters - Responses However, `Parameters` there only includes query parameters (ie, `endpoint?PARAMETER_NAME`), not path parameters...
This is critically important - there is no automated testing. We need unit and/or end-to-end testing examining as many scenarios as possible. (edit: we do have E2E testing now but...
Add automatic type checking using Pipelines so we can have some checks before merging a PR.
Consider condensing or using a grid layout
Currently installing the program results in a number of errors due to unsigned binaries. We can improve the experience by signing them.
Is `@param - description` a valid alternative for `@typeParam T - description`? It's marked as invalid in the playground but is provided as an example [in the docs](https://tsdoc.org/pages/tags/typeparam/): ```ts /**...
Sometimes you have a generic base interface type that you extend from, and you want to documenting a member of the extending interface without having to redeclare that member. In...
Currently, the emitter seems to have no option or support for breaking lines at a certain length. If a parameter description has a 500-character block of text, all of that...
According to the readme, `@param` and `@returns` should go together in a group like so: ```ts /** * Returns the average of two numbers. * * @remarks * This method...
First, updated the slots tests to that the `context` prop is not always defined. This caused the tests to fail due to infinite rendering, as expected from #2187. Then, fixed...