Files
zeekay b0db427c79 regenerate from cloud 939b09d4
The projection was 113 commits behind the document it claims to describe, and
`generate.py --all --check` reported every one of the thirteen clients DRIFTED —
the same +19 models in each, because they all fell behind the same emission.

Regenerated in place from hanzo-inc/cloud openapi.yaml at 939b09d4
(sha256 087024f6…), which is the only description of this API that cannot name a
route the binary does not serve. `--check` is clean across all thirteen after.

.spec-lock moved with the code. The generator READS that file and never writes
it — hanzoai/ci`s lane does — so a hand run leaves every lock naming the previous
document. A lock that disagrees with the tree beside it is worse than no lock:
the next `--check` without `--spec` fetches what production serves, compares it
to a digest that was already wrong, and reports drift that is really staleness.
2026-08-24 23:32:45 -07:00

36 lines
1.1 KiB
Swift

//
// ProviderInfo.swift
//
// Generated by openapi-generator
// https://openapi-generator.tech
//
import Foundation
public struct ProviderInfo: Sendable, Codable, ParameterConvertible, Hashable {
/** DisplayName is the human label for the sign-in button; this deployment sends \"Hanzo\". Omitted from the body when empty. */
public var displayName: String?
/** Name is the provider id, and it is the value that goes back in the URL to start a login: GET /v1/team/account/auth/{provider}. This deployment surfaces exactly one, \"openid\" — the hanzo.id provider. */
public var name: String?
public init(displayName: String? = nil, name: String? = nil) {
self.displayName = displayName
self.name = name
}
public enum CodingKeys: String, CodingKey, CaseIterable {
case displayName
case name
}
// Encodable protocol methods
public func encode(to encoder: Encoder) throws {
var container = encoder.container(keyedBy: CodingKeys.self)
try container.encodeIfPresent(displayName, forKey: .displayName)
try container.encodeIfPresent(name, forKey: .name)
}
}