Adding API documentation #56

New Issue

Jef Roosens · 2021-05-01T10:20:55+02:00

Jef Roosens commented

2021-05-01 10:20:55 +02:00

The API needs to be documented, e.g. using Swagger.

We can use this repo as inspiration. It uses a YAML file (There's several in this repo, but the idea is the same) to describe the API, according to the OpenAPI 3.0 Spec.

This looks like a good tutorial. We can also look at Swagger, a popular alternative.

The API needs to be documented, e.g. using Swagger. We can use [this repo](https://github.com/firefly-iii/api-docs-generator) as inspiration. It uses a [YAML file](https://github.com/firefly-iii/api-docs-generator/blob/main/yaml/paths/attachments.yaml) (There's several in this repo, but the idea is the same) to describe the API, according to the [OpenAPI 3.0 Spec](https://swagger.io/specification/). [This](https://support.smartbear.com/swaggerhub/docs/tutorials/openapi-3-tutorial.html) looks like a good tutorial. We can also look at [Swagger](https://support.smartbear.com/swaggerhub/docs/tutorials/writing-swagger-definitions.html), a popular alternative.

Jef Roosens added this to the Fej 1.1.0 - The Calm before the Storm milestone 2021-05-01 10:20:55 +02:00

Jef Roosens added the

project/backend

Brainstorm

labels 2021-05-01 10:20:55 +02:00

Jef Roosens self-assigned this 2021-05-01 10:20:56 +02:00

Jef Roosens added this to the Fej 1.1.0 project 2021-05-01 10:20:56 +02:00

Sign in to join this conversation.