Skip to content

Track proposal for namespace-based generated types file splitting #929

Description

@nac5504

Description

Track the public proposal and review discussion for opt-in namespace-based file splitting of generated Types.swift output.

Related PRs:

The intended proposal scope is limited to the implementation in #925:

  • Add an opt-in namespace file-splitting strategy for generated types.
  • Keep default generation unchanged: one Types.swift file.
  • When enabled, emit:
    • Types.swift for root declarations
    • Types+Components.swift for the generated Components namespace
    • Types+Operations.swift for the generated Operations namespace
  • Keep generated adopter-facing API names unchanged.
  • Leave more advanced sharding strategies, such as dependency-aware or count-based splitting, to future proposals if benchmarks justify the added complexity.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementImprovements to existing feature.status/triageCollecting information required to triage the issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions