tsdoc/tsdoc-config
Pete Gonzalez 96b65ded21 PR feedback 2023-06-11 22:45:09 -07:00
..
.vscode Convert all project configurations to use Heft rigs 2020-11-24 19:28:51 -08:00
config Fix up projects to build again 2023-06-10 15:53:21 -07:00
src PR feedback 2023-06-11 22:45:09 -07:00
.eslintrc.js Invoke "prettier . --write" to prettify all source files 2020-11-24 20:12:30 -08:00
.npmignore Normalize .npmignore and .npmrc files 2020-11-24 19:27:53 -08:00
.npmrc Normalize .npmignore and .npmrc files 2020-11-24 19:27:53 -08:00
.prettierrc.json Add new project tsdoc-config 2019-11-15 00:06:08 -08:00
CHANGELOG.json Deleting change files and updating change logs for package updates. 2022-09-14 02:55:06 +00:00
CHANGELOG.md Deleting change files and updating change logs for package updates. 2022-09-14 02:55:06 +00:00
LICENSE Add new project tsdoc-config 2019-11-15 00:06:08 -08:00
README.md Rename master to main. 2022-04-08 19:07:34 -07:00
package.json Upgrade dependencies, switch to useWorkspace=true 2023-06-10 15:27:37 -07:00
tsconfig.json Convert all project configurations to use Heft rigs 2020-11-24 19:28:51 -08:00

README.md

@microsoft/tsdoc-config

TSDoc is a proposal to standardize the doc comments used in TypeScript source files. The main package @microsoft/tsdoc implements the TSDoc parser. The @microsoft/tsdoc-config package is an optional add-on for loading the tsdoc.json file format that enables users to define custom TSDoc tags. (This functionality was moved to its own package because it requires external dependencies such as NodeJS and ajv, whereas the main package is fully self-contained.)

For more information about TSDoc, please visit the project website:

https://tsdoc.org

Creating config files

The tsdoc.json file is optional. When used, it is expected to be found in the same folder as the tsconfig.json file for a project. The loader looks for it by walking upwards in the directory tree until it finds a folder containing tsconfig.json or package.json, and then it attempts to load tsdoc.json from that location.

The tsdoc.json file conforms to the tsdoc.schema.json JSON schema. It defines tags using similar fields as the TSDocTagDefinition API used by TSDocParser from @microsoft/tsdoc.

Here's a simple example:

tsdoc.json

{
  "$schema": "https://developer.microsoft.com/json-schemas/tsdoc/v0/tsdoc.schema.json",
  "tagDefinitions": [
    {
      "tagName": "@myTag",
      "syntaxKind": "modifier"
    }
  ]
}

If you want to define custom tags in one place and share them across multiple projects, the extends field specifies a list of paths that will be mixed in with the current file:

tsdoc.json

{
  "$schema": "https://developer.microsoft.com/json-schemas/tsdoc/v0/tsdoc.schema.json",
  "extends": [
    "my-package/dist/tsdoc-base.json",
    "./path/to/local/file/tsdoc-local.json"
  ]
}

NOTE: The extends paths are resolved using NodeJS module resolution, so local paths must begin with ./ to avoid being interpreted as an NPM package name.

API Usage

The code sample below illustrates how to invoke the @microsoft/tsdoc-config API to load a tsdoc.json file:

import * as path from 'path';
import { TSDocParser, TSDocConfiguration } from '@microsoft/tsdoc';
import { TSDocConfigFile } from '@microsoft/tsdoc-config';

// Sample source file to be parsed
const mySourceFile: string = 'my-project/src/example.ts';

// Load the nearest config file, for example `my-project/tsdoc.json`
const tsdocConfigFile: TSDocConfigFile = TSDocConfigFile.loadForFolder(path.dirname(mySourceFile));
if (tsdocConfigFile.hasErrors) {
  // Report any errors
  console.log(tsdocConfigFile.getErrorSummary());
}

// Use the TSDocConfigFile to configure the parser
const tsdocConfiguration: TSDocConfiguration = new TSDocConfiguration();
tsdocConfigFile.configureParser(tsdocConfiguration);
const tsdocParser: TSDocParser = new TSDocParser(tsdocConfiguration);