Typedoc is able to output a JSON schema. We should look into including it in the docs site, in order to be able to use it as a schema to support auto-complete and linting in IDEs. For example, if it would allow us to write something like this:
{
"$schema": "https://jsfkit.github.io/types/schema.json",
"name": "foo.xlsx",
"sheeets": [
{
"name": "Sheet1",
"cells": {
"A1": { "v": 10 }
}
}
],
"names": [],
"calculationProperties": {
"iterate": false,
"iterateCount": 100,
"iterateDelta": 0.001,
"epoch": 1900
}
}
And get IDEs to complain about the missing properties and misspelling of sheeets, then we're onto a good thing.
Typedoc is able to output a JSON schema. We should look into including it in the docs site, in order to be able to use it as a schema to support auto-complete and linting in IDEs. For example, if it would allow us to write something like this:
{ "$schema": "https://jsfkit.github.io/types/schema.json", "name": "foo.xlsx", "sheeets": [ { "name": "Sheet1", "cells": { "A1": { "v": 10 } } } ], "names": [], "calculationProperties": { "iterate": false, "iterateCount": 100, "iterateDelta": 0.001, "epoch": 1900 } }And get IDEs to complain about the missing properties and misspelling of
sheeets, then we're onto a good thing.