Skip to content

[scala][sttp]convert header parameter to string#11991

Merged
wing328 merged 1 commit intoOpenAPITools:masterfrom
bgong-mdsol:fix/scala-sttp-headerparam-creation
Mar 30, 2022
Merged

[scala][sttp]convert header parameter to string#11991
wing328 merged 1 commit intoOpenAPITools:masterfrom
bgong-mdsol:fix/scala-sttp-headerparam-creation

Conversation

@bgong-mdsol
Copy link
Contributor

This PR fixes the issue #11942

Here is the openapi spec for reproduce the issue and verify the fix.

openapi: 3.0.0
info:
  title: Request Header
  version: "1.0.0"
paths:
  /test:
    get:
      summary: Empty Route
      parameters:
      - description: Gets user info.
        explode: false
        in: header
        name: user_uuid
        required: true
        schema:
          format: uuid
          type: string
        style: simple
      responses:
        "200":
          description: Good Request.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReturnValue'
        "400":
          description: Bad Request.
components:
  schemas:
    ReturnValue:
      properties:
        name:
          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:
    ./mvnw clean package 
    ./bin/generate-samples.sh
    ./bin/utils/export_docs_generators.sh
    
    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 ./bin/generate-samples.sh bin/configs/java*.
    For Windows users, please run the script in Git BASH.
  • 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

@wing328
Copy link
Member

wing328 commented Mar 30, 2022

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants