OpenAPITools / OpenAPITools/openapi-generator
[BUG] Operation parameters resolved to an enum do not have access to underlying model
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
In this file bin\configs\csharp-generichost-latest-nrt.yaml I appended this yaml
skipFormModel: false
inlineSchemaOptions:
RESOLVE_INLINE_ENUMS: true
The sample then does not compile.
I need to change WriteString to WriteNumber. To do that, I need access to the CodegenModel, however, this is a CodegenProperty. The reason that this is a problem is that the allowableValues are different. In the model, I can do this
{{#allowableValues}}{{#enumVars}}{{#-first}}{{#isString}}{{^isNumeric}}string{{/isNumeric}}{{/isString}}{{^isString}}{{#isNumeric}}number{{/isNumeric}}{{/isString}}{{/-first}}{{/enumVars}}{{/allowableValues}}
If you look in the image above, you can see I printed the CodegenProperty {{#allowableValues}}{{#enumVars}}{{#-first}} but there is no isNumeric, so I can't fix this.
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
Start with bin\configs\csharp-generichost-latest-nrt.yaml and reproduce the compilation failure with RESOLVE_INLINE_ENUMS enabled. Trace the generated C# operation-parameter template where CodegenProperty.allowableValues is inspected, then verify the generated sample compiles with the required string-versus-number enum information available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100