OpenAPI 3.1 documentation for polyproto, powered by TypeSpec https://apidocs.polyproto.org
2025-09-13 18:55:53 +00:00
.github fix: force push 2025-09-13 18:18:19 +02:00
.vscode feat: typespec compilation task for vscode 2025-05-31 12:37:12 +02:00
build chore(bot): update openapi3 schema 2025-09-13 18:55:53 +00:00
polyproto fix: Ed25519 signatures require 128 hex chars 2025-09-13 20:52:52 +02:00
.gitattributes override linguist-language 2024-10-27 22:58:03 +01:00
.gitignore feat: tsp update to 1.0.0, oapi update to 3.1 2025-05-29 15:48:47 +02:00
LICENSE Update LICENSE 2024-12-22 11:48:02 +01:00
package-lock.json chore: update typespec to v1.1.0 2025-06-11 18:31:31 +02:00
README.md feat: add faq shield 2025-06-18 11:45:06 +02:00

a purple cog, split in the middle along the horizontal axis with a gap inbetween the two halves. three overlayed, offset sinus-like waves travel through that gap. each wave has a different shade of purple

typespec-openapi

Code-of-conduct-shield Build/Deploy OpenAPI specification Discord FAQ-shield

Specification documents and API documentation for polyproto, polyproto-chat and polyproto-mls.

API documentation built with TypeSpec.

Pre-compiled OpenAPI schema(s)

Find the pre-compiled OpenAPI v3.1 schema file(s) in the /build directory. The schema is automatically built and deployed to the main branch on every push to the main branch.

Contributing

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 our Code of Conduct and Contributing Guidelines before contributing.

Setting up a development environment

You will need the following things installed on your computer:

  • Node.js >= 20
  • npm. I personally prefer pnpm, but have found it to not work with TypeSpec. Maybe this is a me-issue, but I recommend npm for best compatibility nonetheless.
  • git
  • TypeSpec - install it globally with npm install -g @typespec/compiler
  1. Navigate to the /polyproto directory.
  2. Select the project you want to compile. In this example, we are compiling the core project. Navigate to that directory.
  3. Run tsp install to install the dependencies.
  4. Run tsp compile . to compile the project or tsp compile --watch . to automatically recompile the project when you save a file.
  5. The compiled OpenAPI3 schema will be in the $PROJECT/tsp-output/@typespec/openapi3 directory.