@swagger-api/apidom-parser-adapter-json

@swagger-api/apidom-parser-adapter-json is a parser adapter for the JSON format.

CST produced by lexical analysis is syntactically analyzed and
ApiDOM structure using base ApiDOM namespace is produced.

Installation

After prerequisites for installing this package are satisfied, you can install it
via npm CLI by running the following command:

``sh
$ npm install @swagger-api/apidom-parser-adapter-json
`

Parse phases

The parse stage takes JSON string and produces ApiDOM structure using base ApiDOM namespace.
There are two phases of parsing: Lexical Analysis and Syntactic Analysis.

$3

Lexical Analysis will take a JSON string and turn it into a stream of tokens.
tree-sitter / web-tree-sitter is used as an underlying lexical analyzer.

$3

Syntactic Analysis will take a stream of tokens and turn it into an ApiDOM representation.
CST produced by lexical analysis is syntactically analyzed
and ApiDOM structure using base ApiDOM namespace is produced.

#### Direct Syntactical analysis

This analysis directly turns tree-sitter CST into ApiDOM. Single traversal is required which makes
it super performant, and it's the default analysis used.

`js
import { parse } from '@swagger-api/apidom-parser-adapter-json';

const parseResult = await parse('{"prop": "value"}', {
syntacticAnalysis: 'direct',
});
`

#### Indirect Syntactic analysis

This analysis turns trees-sitter CST into JSON AST representation.
Then JSON AST is turned into ApiDOM. Two traversals are required, which makes indirect analysis less performant than direct one.
Thought less performant, having JSON AST representation allows us to do further complex analysis.

`js
import { parse } from '@swagger-api/apidom-parser-adapter-json';

const parseResult = await parse('{"prop": "value"}', {
syntacticAnalysis: 'indirect',
});
`

Parser adapter API

This parser adapter is fully compatible with parser adapter interface required by @swagger-api/apidom-parser
and implements all required properties.

$3

Defines list of media types that this parser adapter recognizes.

`js
['application/json']
`

$3

Detection is based on a regular expression matching valid JSON data types to indicate whether the provided source string is or isn't JSON string.

$3

This adapter exposes an instance of base ApiDOM namespace.

$3

parse function consumes various options as a second argument. Here is a list of these options:

Option | Type | Default | Description
--- | --- | --- | ---
sourceMap | Boolean | false | Indicate whether to generate source maps.
syntacticAnalysis | String | direct | Indicate type of syntactic analysis

All unrecognized arbitrary options will be ignored.

Usage

This parser adapter can be used directly or indirectly via @swagger-api/apidom-parser.

$3

During direct usage you don't need to provide mediaType as the parse function is already pre-bound
with supported media types.

`js
import { parse, detect } from '@swagger-api/apidom-parser-adapter-json';

// detecting
await detect('{"prop": "value"}'); // => true
await detect('test'); // => false

// parsing
const parseResult = await parse('{"prop": "value"}', { sourceMap: true });
`

$3

You can omit the mediaType option here, but please read Word on detect vs mediaTypes before you do so.

`js
import ApiDOMParser from '@swagger-api/apidom-parser';
import * as jsonParserAdapter from '@swagger-api/apidom-parser-adapter-json';

const parser = new ApiDOMParser();

parser.use(jsonParserAdapter);

const parseResult = await parser.parse('{"prop", "value"}', { mediaType: jsonParserAdapter.mediaTypes.latest('json') });
``