Created by: bgong-mdsol
This PR fixes the issue #8827
Here is the openapi spec that can be used to reproduce the issue and verify the fix. This spec includes the both inline and stand-alone Enum schemas.
openapi: 3.0.3
info:
title: standalone or inline enums
version: '1.0'
paths:
/state:
get:
operationId: getUsers
responses:
'200':
description: get Users
content:
application/json:
schema:
$ref: '#/components/schemas/Users'
components:
schemas:
Users:
properties:
emails:
items:
type: string
type: array
search:
enum:
- email
- full_name
type: string
standAloneEnum:
$ref: '#/components/schemas/StandAloneEnum'
StandAloneEnum:
enum:
- first_name
- last_name
- email
type: string
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master(5.3.0) -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.
@chameleon82 @clasnake @jimschubert @shijinkui @ramzimaalej @Bouillie @wing328 @jfeltesse-mdsol @jcarres-mdsol