- Notifications
You must be signed in to change notification settings - Fork2
OpenAPI 3.1 documentation for polyproto, powered by TypeSpec
License
polyphony-chat/typespec-openapi
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
Specification documents and API documentation forpolyproto
,polyproto-chat
andpolyproto-mls
.
API documentation built withTypeSpec.
Find the pre-compiled OpenAPI v3.1 schema file(s) in the/build
directory. The schema is automatically built and deployed to themain
branch on every push to themain
branch.
The best way to contribute is to open an issue if you find any problems with the documentation. Creating an issue is generally the best way to contribute to any open source project. Issues allow for an exchange between contributors and maintainers to discuss the viability of implementing an issue, usually minimizing frustration.
You should also read ourCode of Conduct andContributing Guidelines before contributing.
You will need the following things installed on your computer:
Node.js >= 20
npm
. I personally preferpnpm
, but have found it tonot work with TypeSpec. Maybe this isa me-issue, but I recommendnpm
for best compatibility nonetheless.git
TypeSpec
- install it globally withnpm install -g @typespec/compiler
- Navigate to the
/polyproto
directory. - Select the project you want to compile. In this example, we are compiling the
core
project.Navigate to that directory. - Run
tsp install
to install the dependencies. - Run
tsp compile .
to compile the project ortsp compile --watch .
to automatically recompilethe project when you save a file. - The compiled OpenAPI3 schema will be in the
$PROJECT/tsp-output/@typespec/openapi3
directory.
About
OpenAPI 3.1 documentation for polyproto, powered by TypeSpec
Topics
Resources
License
Code of conduct
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.
Contributors4
Uh oh!
There was an error while loading.Please reload this page.