Skip to content

[Docs] Add a link to the WWDC talk #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 11, 2023
Merged

[Docs] Add a link to the WWDC talk #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,8 @@ The Swift OpenAPI Generator project is split across multiple repositories to ena

**swift-openapi-runtime** ([source][repo-runtime], [docs][docs-runtime]) provides a library with common types and abstractions used by the generated code.

> See the generator in action in [Meet Swift OpenAPI Generator](https://developer.apple.com/wwdc23/10171) from WWDC23.

Choose one of the transports listed below, or create your own by adopting the `ClientTransport` or `ServerTransport` protocol:

| Repository | Type | Description |
Expand Down
2 changes: 2 additions & 0 deletions Sources/swift-openapi-generator/Documentation.docc/Swift-OpenAPI-Generator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ The Swift OpenAPI Generator project is split across multiple repositories to ena

**swift-openapi-runtime** ([source][repo-runtime], [docs][docs-runtime]) provides a library with common types and abstractions used by the generated code.

> Tip: See the generator in action in [Meet Swift OpenAPI Generator](https://developer.apple.com/wwdc23/10171) from WWDC23.

The generated code isn't tied to a specific HTTP client library or web server framework, allowing adopters to use simple input and output data types for API operations. For making and serving HTTP requests, the generated code requires a type that confoms to one of the protocol abstractions, `ClientTransport` or `ServerTransport`, which the user chooses when creating the client or server.

Choose one of the transports listed below, or create your own by adopting the `ClientTransport` or `ServerTransport` protocol:
Expand Down