Documentation Tests
Deno supports type-checking your documentation examples.
No runtime behavior is tested for code snippets in documentation as of now. Tracking issue: denoland/deno#4716
This makes sure that examples within your documentation are up to date and working.
The basic idea is this:
/**
* # Examples
*
* ```ts
* const x = 42;
* ```
*/
The triple backticks mark the start and end of code blocks, the language is determined by the language identifier attribute which may be any of the following:
js
javascript
mjs
cjs
jsx
ts
typescript
mts
cts
tsx
If no language identifier is specified then the language is inferred from media type of the source document that the code block is extracted from.
Another attribute supported is ignore
, which tells the test runner to skip
type-checking the code block.
/**
* # Does not pass type check
*
* ```typescript ignore
* const x: string = 42;
* ```
*/
If this example was in a file named foo.ts, running deno test --doc foo.ts
will extract this example, and then type-check it as a standalone module living
in the same directory as the module being documented.
To document your exports, import the module using a relative path specifier:
/**
* # Examples
*
* ```ts
* import { foo } from "./foo.ts";
* ```
*/
export function foo(): string {
return "foo";
}
Help us make these docs great!
Make a contribution
Deno's docs are open source. See something that's wrong or unclear? Submit a pull request:
Edit this page