This PR contains the work done to cleans up the library after the Swift 6.2 migration: drops the legacy conditional-compilation paths, hardens the OpenAPI specification, removes boilerplate from the live client, and makes the live test suite resilient to changes in the upstream service data.
* Swift 6.2 baseline
* Adopted swift-tools-version: 6.2, which allowed removing every #if swift(>=6.0) / #if swift(>=6.2) branch and natural-language test names are now the only code paths.
* `AmiiboClient` client now refines `Sendable`, and both `AmiiboLiveClient` and `AmiiboService` conform to it, so instances can be shared across concurrency domains.
* Live client
* Extracted a generic `perform(_:)` helper that wraps every generated API call and funnels transport errors through the existing error mapper — replaces six repeated do/catch blocks and lets the private fetch* methods use typed throws end-to-end.
* Added the internal `KeyNamePayload` protocol and a generic makeModels(from:), collapsing the four near-identical mapping/sorting blocks for amiibo series, types, game characters and game series into one.
* The server URL is now resolved once into a static let constant instead of on every initialization.
* Improved error mapping: URLError.cancelled → .cancelled, .cannotParseResponse → .decoding, and .dataNotAllowed, .internationalRoamingOff, .secureConnectionFailed now map to .notAvailable.
* Simplified the Amiibo.Platform initializer ([Amiibo+Platform.swift](vscode-webview://1m6rk4uhpaukb4hrbp3j54p77iq693fq2ql7o9oup2pca1omf7f6/Sources/AmiiboService/Public/Models/Amiibo/Amiibo+Platform.swift)) using optional chaining and ?? [] instead of nested guards and immediately-invoked closures.
* Set the en_US_POSIX locale on both fixed-format date formatters so the user's locale or 12/24-hour setting can no longer break parsing.
* OpenAPI specification
* Replaced the shared Tuple schema with explicit per-type schemas (AmiiboSeries, AmiiboType, GameCharacter, GameSeries), so the generated code exposes real properties instead of allOf wrappers with .value1 accessors.
* Extracted named list schemas (AmiiboList, AmiiboSeriesList, …) for the wrapper payloads, which turns the generated .case2 enum cases into readable .AmiiboSeriesList cases.
* Added validation patterns and length bounds to the id, head, tail and key query parameters, and collapsed the redundant pattern/minLength/maxLength triplets on head/tail into ^[0-9a-fA-F]{8}$.
* Extracted the shared InternalServerError response, replacing the five inline 500 descriptions.
* Documented the two non-standard date/time decoding behaviours (date-only strings for release dates, offset-less timestamps for lastUpdated) and why the optional amiibo wrapper property must stay optional.
* Corrected the info.version value from v1.0.0 to 1.0.0.
* ⚠️ Breaking changes
* Minimum Swift version raised from 5.10 to 6.2.
* `AmiiboServiceError.unknown` now carries a String description of the underlying error.
* `AmiiboClient` requires Sendable conformance, so existing custom mock clients must be Sendable.
Reviewed-on: #28
Co-authored-by: Javier Cicchelli <javier@rock-n-code.com>
Co-committed-by: Javier Cicchelli <javier@rock-n-code.com>
165 lines
5.1 KiB
Markdown
165 lines
5.1 KiB
Markdown
# ``AmiiboService``
|
|
|
|
A library that provides everything the developer needs to interact with the **Amiibo API** backend service.
|
|
|
|
## Overview
|
|
|
|
The `amiibo-service` library is a package that allows the developer to interact with the [Amiibo API](https://www.amiiboapi.org) backend service seamlessly, by not only providing the *service* type but also any possible *models*, *filters*, *errors* and *interfaces* types that might be needed during implementation.
|
|
|
|
## Design
|
|
|
|
Although it could have been possible to generate a one-to-one RESTful client based on the Open API specification document that describe the available endpoints of the backend service, it was decided to design a `AmiiboService` service type that removes the complexities of the API design imposed by the backend service, and provides the developer with a simple interface, and a seamless experience.
|
|
|
|
## Installation
|
|
|
|
To use the `AmiiboService` library with your package, then add it as a dependency in the `Package.swift` file:
|
|
|
|
```swift
|
|
let package = Package(
|
|
// name, platforms, products, etc.
|
|
dependencies: [
|
|
.package(url: "https://github.com/rock-n-code/amiibo-service", from: "2.0.0"),
|
|
// other dependencies
|
|
],
|
|
targets: [
|
|
.target(
|
|
name: "SomeTarget",
|
|
dependencies: [
|
|
.product(name: "AmiiboService", package: "amiibo-service"),
|
|
]
|
|
)
|
|
// other targets
|
|
]
|
|
)
|
|
```
|
|
|
|
It is also possible to use the `AmiiboService` library with your app in Xcode, then add it as a dependency in your Xcode project.
|
|
|
|
> important: Swift 6.2 or higher is required in order to compile this library.
|
|
|
|
## Usage
|
|
|
|
Create an ``AmiiboService`` instance and call any of its endpoints. Each endpoint accepts an optional filter and, when omitted, returns the full set of results:
|
|
|
|
```swift
|
|
import AmiiboService
|
|
|
|
let service = AmiiboService()
|
|
|
|
// Fetch all amiibos
|
|
let amiibos = try await service.getAmiibos()
|
|
|
|
// Fetch amiibos filtered by name
|
|
let zeldaAmiibos = try await service.getAmiibos(.init(name: "zelda"))
|
|
|
|
// Fetch amiibo series, types, game characters, and game series
|
|
let series = try await service.getAmiiboSeries()
|
|
let types = try await service.getAmiiboTypes()
|
|
let characters = try await service.getGameCharacters()
|
|
let gameSeries = try await service.getGameSeries()
|
|
|
|
// Fetch the last updated timestamp
|
|
let lastUpdated = try await service.getLastUpdated()
|
|
```
|
|
|
|
## Caching
|
|
|
|
The [Amiibo API](https://www.amiiboapi.org) recommends that consumers who call the API regularly implement caching on their systems. This library does not include a built-in cache, leaving the choice of caching strategy to the consumer. The following examples show two common approaches.
|
|
|
|
### URLCache on the transport layer
|
|
|
|
Pass a custom `URLSessionTransport` with a cache-configured `URLSession` to ``AmiiboLiveClient``:
|
|
|
|
```swift
|
|
import OpenAPIURLSession
|
|
|
|
let configuration = URLSessionConfiguration.default
|
|
|
|
configuration.urlCache = URLCache(
|
|
memoryCapacity: 5_000_000,
|
|
diskCapacity: 50_000_000
|
|
)
|
|
|
|
let transport = URLSessionTransport(
|
|
configuration: .init(
|
|
session: URLSession(configuration: configuration)
|
|
)
|
|
)
|
|
|
|
let service = AmiiboService(
|
|
client: AmiiboLiveClient(transport: transport)
|
|
)
|
|
```
|
|
|
|
This leverages HTTP cache headers from the server and persists cached responses to disk.
|
|
|
|
### Application-level caching
|
|
|
|
Alternatively, cache the results returned by ``AmiiboService`` directly in your application using any storage mechanism that fits your needs, such as an in-memory dictionary, a database, or a file-based store.
|
|
|
|
## Testing
|
|
|
|
The ``AmiiboClient`` protocol enables creating custom mock clients for testing, eliminating the need for network calls in unit tests. Conform to ``AmiiboClient`` and return stubbed data or throw ``AmiiboServiceError`` errors to verify your application's behavior:
|
|
|
|
```swift
|
|
import AmiiboService
|
|
|
|
struct MyMockClient: AmiiboClient {
|
|
var error: AmiiboServiceError?
|
|
|
|
func getAmiibos(
|
|
by filter: AmiiboFilter
|
|
) async throws(AmiiboServiceError) -> [Amiibo] {
|
|
if let error { throw error }
|
|
return []
|
|
}
|
|
|
|
// Implement remaining protocol requirements...
|
|
}
|
|
|
|
let service = AmiiboService(client: MyMockClient())
|
|
```
|
|
|
|
Inject the mock client into ``AmiiboService`` via its ``AmiiboService/init(client:)`` initializer to test how your code handles empty results, specific errors, or any other scenario without relying on the live backend.
|
|
|
|
## Tasks
|
|
|
|
This library offers a set of ready-to-use tasks that simplify the interaction with the library, which the developer can use from any `Terminal` application.
|
|
|
|
> Tip: To show the available list of tasks, plus display some explanations about each and every one of them; please enter the following command:
|
|
|
|
```bash
|
|
$ make
|
|
```
|
|
|
|
## Topics
|
|
|
|
### Service
|
|
|
|
- ``AmiiboService``
|
|
|
|
### Clients
|
|
|
|
- ``AmiiboClient``
|
|
- ``AmiiboLiveClient``
|
|
|
|
### Models
|
|
|
|
- ``Amiibo``
|
|
- ``AmiiboSeries``
|
|
- ``AmiiboType``
|
|
- ``GameCharacter``
|
|
- ``GameSeries``
|
|
|
|
### Filters
|
|
|
|
- ``AmiiboFilter``
|
|
- ``AmiiboSeriesFilter``
|
|
- ``AmiiboTypeFilter``
|
|
- ``GameCharacterFilter``
|
|
- ``GameSeriesFilter``
|
|
|
|
### Errors
|
|
|
|
- ``AmiiboServiceError``
|