apple / apple/swift-openapi-generator
Multipart generated enum case naming is inconsistent (other vs additionalProperties)
- Dominant language
- Swift
- Stars
- 2k
- Forks
- 182
- Avg merge
- 13h 28m
- Merged PRs (30d)
- 5
Description
### Description
The generated code doesn't follow the multipart SOAR proposal, see details in https://github.com/apple/swift-openapi-generator/issues/596
### Reproduction
See the example in https://github.com/apple/swift-openapi-generator/issues/596.
### Package version(s)
On main.
### Expected behavior
Consistent behavior that matches the proposal.
### Environment
Xcode 16 Beta.
### Additional information
_No response_
Contributor guide
Research direction
Start by reading the multipart SOAR proposal and the reproduction linked in issue #596, then inspect where multipart enum cases are generated. Compare the `other` and `additionalProperties` cases with the proposal; the work is done when their naming is consistent with it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, swift
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100