If using Cocoapods (not sure if true for other DMs), public struct {{ options.name }} will be matching your generated API client Swift module name which breaks types lookup. For example, if your codebase or another module has a type User and your generated API client has User, then referencing User from generated API client via {{ options.name }}.User won't work.
Suggest moving away from public struct {{ options.name }} by splitting it up into public struct Config that holds coding options and Server and public struct Operation to namespace operations.
If using Cocoapods (not sure if true for other DMs),
public struct {{ options.name }}
will be matching your generated API client Swift module name which breaks types lookup. For example, if your codebase or another module has a typeUser
and your generated API client hasUser
, then referencingUser
from generated API client via{{ options.name }}.User
won't work.Apparently, it's a limitation of Swift compiler - https://bugs.swift.org/browse/SR-1386
Suggest moving away from
public struct {{ options.name }}
by splitting it up intopublic struct Config
that holds coding options and Server andpublic struct Operation
to namespace operations.What do you think @yonaskolb ?