Swiftgger is simple library which generate output compatible with OpenAPI version 3.0.1. Library is generating objects tree which you can serialize to JSON and return by your API endpoint. URL to that endpoint can be used in Swagger UI. Thanks to this you have GUI which shows you exactly how your API looks like and you can use that GUI to execute actions (requests). It's especially helpful during API testing.
Swiftgger support Swift Package Manager. You have to add to your Package.swift file information about Swiftgger. Below is a simple example.
let package = Package(
name: "YourApp",
dependencies: [
.package(url: "https://github.com/mczachurski/Swiftgger.git", from: "1.2.1")
],
targets: [
.target(name: "YourApp", dependencies: ["Swiftgger"]),
.testTarget(name: "YourAppTests", dependencies: ["YourApp"])
]
)Then you have to run: swift build command.
Unfortunately Swift is not perfect in reflection (introspection) and a lot of settings we have to do manually.
OpenAPIBuilder is main object which is responsible for collect information about our API structure and generating OpenAPI response. It contains some basic information about API like title, version, author, license etc.
let openAPIBuilder = OpenAPIBuilder(
title: "Tasker server API",
version: "1.0.0",
description: "This is a sample server for task server application.",
termsOfService: "http://example.com/terms/",
contact: APIContact(name: "John Doe", email: "[email protected]", url: URL(string: "http://example-domain.com/@john")),
license: APILicense(name: "MIT", url: URL(string: "http://mit.license")),
authorizations: [.jwt(description: "You can get token from *sign-in* action from *Account* controller.")]
)We can use openAPIBuilder object if we want to specify list of controllers and actions.
Adding information about controller is pretty simple. We have to execute add method on OpenAPIBuilder object.
openAPIBuilder.add(
APIController(name: "Users", description: "Controller where we can manage users", actions: [])
)Each controller can have list of actions (routes) with name, description, response and requests information.
Get by id action
APIAction(method: .get, route: "/users/{id}",
summary: "Getting user by id",
description: "Action for getting specific user from server",
parameters: [
APIParameter(name: "id", description: "User id", required: true)
],
responses: [
APIResponse(code: "200", description: "Specific user", object: UserDto.self),
APIResponse(code: "404", description: "User with entered id not exists"),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
)Post action
APIAction(method: .post, route: "/users",
summary: "Adding new user",
description: "Action for adding new user to the server",
request: APIRequest(object: userDto, description: "Object with user information."),
responses: [
APIResponse(code: "200", description: "User data after adding to the system", object: UserDto.self),
APIResponse(code: "400", description: "There was issues during adding new user", object: ValidationErrorResponseDto.self),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
)Besides controllers and actions we have to specify list of objects which can be used in API. We can do this like on following snippet.
openAPIBuilder.add([
APIObject(object: UserDto(id: UUID(), createDate: Date(), name: "John Doe", email: "[email protected]", isLocked: false)),
APIObject(object: ValidationErrorResponseDto(message: "Object is invalid", errors: ["property": "Information about error."]))
])Below there is an example how to configure full CRUD operation. Of course in that example whole configuration is done in one place. However in your application you can put endpoint/actions configuration near your implementation (separate for each action).
// Create builder.
let openAPIBuilder = OpenAPIBuilder(
title: "Tasker server API",
version: "1.0.0",
description: "This is a sample server for task server application.",
authorizations: [.jwt(description: "You can get token from *sign-in* action from *Account* controller.")]
)
.add(APIController(name: "Users", description: "Controller where we can manage users", actions: [
APIAction(method: .get, route: "/users",
summary: "Getting all users",
description: "Action for getting all users from server",
responses: [
APIResponse(code: "200", description: "List of users", object: UserDto.self),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
),
APIAction(method: .get, route: "/users/{id}",
summary: "Getting user by id",
description: "Action for getting specific user from server",
parameters: [
APIParameter(name: "id", description: "User id", required: true)
],
responses: [
APIResponse(code: "200", description: "Specific user", object: UserDto.self),
APIResponse(code: "404", description: "User with entered id not exists"),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
),
APIAction(method: .post, route: "/users",
summary: "Adding new user",
description: "Action for adding new user to the server",
request: APIRequest(object: UserDto.self, description: "Object with user information."),
responses: [
APIResponse(code: "200", description: "User data after adding to the system", object: UserDto.self),
APIResponse(code: "400", description: "There was issues during adding new user", object: ValidationErrorResponseDto.self),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
),
APIAction(method: .put, route: "/users/{id}",
summary: "Updating user",
description: "Action for updating specific user in the server",
parameters: [
APIParameter(name: "id", description: "User id", required: true)
],
request: APIRequest(object: UserDto.self, description: "Object with user information."),
responses: [
APIResponse(code: "200", description: "User data after adding to the system", object: UserDto.self),
APIResponse(code: "400", description: "There was issues during updating user", object: ValidationErrorResponseDto.self),
APIResponse(code: "404", description: "User with entered id not exists"),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
),
APIAction(method: .delete, route: "/users/{id}",
summary: "Deleting user",
description: "Action for deleting user from the database",
parameters: [
APIParameter(name: "id", description: "User id", required: true)
],
responses: [
APIResponse(code: "200", description: "User was deleted"),
APIResponse(code: "404", description: "User with entered id not exists"),
APIResponse(code: "401", description: "User not authorized")
],
authorization: true
)
])
)
.add([
APIObject(object: UserDto(id: UUID(), createDate: Date(), name: "John Doe", email: "[email protected]", isLocked: false)),
APIObject(object: ValidationErrorResponseDto(message: "Object is invalid", errors: ["property": "Information about error."]))
])When you prepared configuration for all your controllers/actions then you have to execute following code:
let document = try openAPIBuilder.built()Object document stores information about your API and it's compatible with OpenAPI standard. Now you have to serialize that object to JSON and expose by additional endpoint in your API application for GUI (client) applications.
Swagger UI is great tool which visualize for example request model, parameters etc.
You have also clear list of possible responses which can be returned by your endpoints.
More examples you can find in my other GitHub project.
Tasker server OpenAPI JSON: https://taskerswift.azurewebsites.net/openapi
Tasker server Swagger UI: https://taskerswift-swagger.azurewebsites.net/
This project is licensed under the terms of the MIT license.