OpenAPITools / OpenAPITools/openapi-generator
[BUG][Go][Client] Invalid syntax for nullable binary
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator (example)?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
The generated code has invalid syntax and produces the following error:
syntax error: unexpected * in struct type; possibly missing semicolon or newline or }
openapi-generator version
7.3.0
OpenAPI declaration file content or url
content:
type: string
format: binary
nullable: true
Generates following go struct field:
Content Nullable*os.File `json:"content,omitempty"`
Generation Details
openapi-generator-cli generate -c config.yaml --skip-operation-example
generatorName: go
inputSpec: bcoas1.0.yaml
outputDir: ./lib
packageName: businesscentral
withGoMod: false
Steps to reproduce
Try to use and compile the code. It will fail.
Related issues/PRs
Suggest a fix
Contributor guide
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
Run the reported openapi-generator-cli command with config.yaml and bcoas1.0.yaml, then inspect the generated Go struct containing Content Nullable*os.File. Trace how the nullable binary field is rendered and verify that the generated client compiles without the reported syntax error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100