Api documentation as json or interactively?

Open
#11 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
json, openapi
Domain
api, documentation

Research direction

Start with the linked API documentation and TypeDoc's JSON-generation documentation; compare the proposed .json endpoint with the Swagger/OpenAPI alternative. Done should be a documented, agreed approach for exposing modules and methods in a machine-readable form.

Written by the indexing model from the issue text.

Description

I checked out the api documentation and couldn't find a way to get the modules and methods in a machine readable way. However typedoc states that you can generate json from the comments.

Could we add json somehow, maybe for something like

https://plugins-doc.logseq.com/logseq/baseInfo

it could just be:

https://plugins-doc.logseq.com/logseq/baseInfo.json

An alternative could be something like swagger, which is for OpenApi-documented RESTful apis only. But maybe there exists something comparable for typedoc?!

Dominant language
HTML
Stars
26
Forks
8
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from logseq/plugins

All issues in logseq/plugins

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.