oxidecomputer / oxidecomputer/progenitor
form-data as content type yet to be implemented
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
post:
tags:
- "Voucher"
summary: "Free shit"
description: "No money needed!"
operationId: "uploadVoucher"
requestBody:
description: "File to upload"
content:
form-data:
schema:
properties:
file:
description: "The file to upload"
type: "string"
format: "binary"
type: "object"
Error: UnexpectedFormat("unexpected content type: form-data")
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the OpenAPI requestBody content type is handled until it produces UnexpectedFormat("unexpected content type: form-data"). Use the provided uploadVoucher example as the reproduction case. Done means this form-data request body is accepted and client generation no longer reports that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, rust
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100