Generate API Docs from api-docs/en-us.json
#1209
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a prototype for using the API Docs from api-docs/en-us.json instead of scraping from the DevHub. These docs are much shorter than the current docs and are currently used by JohnnyMorganz/luau-lsp.
I've also gone ahead and pushed the minimum Node version to 20 (the latest LTS version) in order to generate less-verbose JS. The
tsconfig.jsonhas been updated to reflect this.This PR removes
ReflectionMetadata.xmlsupport since it no longer adds any documentation not covered byapi-docs/en-us.json.