swagger-api/swagger-js

Issues

• resolveSubtree does not support 3.1 spec

  #3728 opened 22 days ago by meijey
  0

• Upgrade all @swagger-api dependencies in latest release

  #3721 opened a month ago by paztis
  2

• TypeError: Failed to construct 'URL': Invalid URL

  #3170 opened a year ago by jzrebiec
  11

• Allow passing baseURL to Swagger.exeute method.

  #3537 opened 2 months ago by sauravazad
  4

• I want HTTP request go through a HTTP proxy in the nodejs

  #3679 opened 2 months ago by songtanjichuan
  2

• No way to prevent encoding in serverVariables injection

  #3656 opened 3 months ago by paztis
  4

• V2 Compatibility mode doesn't work for tag interface

  #3635 opened 4 months ago by ansteele
  1

• How to increase timeout on the Swagger Client request

  #3558 opened 4 months ago by virgiawan
  1

• Consider replacing `qs` with `URLSearchParams`

  #3585 opened 4 months ago by wojtekmaj
  2

• swagger_output.json() file can't making endpoint of form type is fileupload .swagger_output.json() can generate simple form not multer type in node with express

  #3599 opened 4 months ago by Ritik558
  1

• OpenAPI 3.1.0 support: align normalization with OpenAPI 2 / 3.0.x

  #3627 opened 5 months ago by char0n
  1

• `These dependencies were not found` when upgrading from `3.18.5` to `3.19.0`

  #3607 opened 5 months ago by mrleblanc101
  2

• The spec for post requests with the "requestBody" parameter does not work.

  #3233 opened 6 months ago by ZababurinSergei
  1

• OpenAPI 3.1: visitors after the dereference visitor don't get mutated elements

  #3520 opened 7 months ago by glowcloud
  4

• Integrate ApiDOM@1.0.0-alpha.x

  #3518 opened 7 months ago by char0n
  1

• Path not resolving correctly if the URL contains space

  #3516 opened 7 months ago by DevyaJha
  2

• [3.27.4 Regression] Multiple path parameters are not all applied

  #3508 opened 8 months ago by kevinoid
  5

• Dependency was not found `@swagger-api/apidom-reference/configuration/empty` after `3.18` to `3.19` upgrade

  #3136 opened a year ago by mrleblanc101
  7

• Fix code scanning alert - Polynomial regular expression used on uncontrolled data

  #3501 opened 8 months ago by char0n
  4

• Escape regular expressions with values passed by the user

  #3505 opened 8 months ago by glowcloud
  1

• Replace regular expressions for path templating

  #3503 opened 8 months ago by glowcloud
  1

• react-native Error: Unable to resolve module @swagger-api/apidom-reference/configuration/empty

  #3411 opened 8 months ago by voydz
  1

• refractor(specmap): integrate specmap into generic resolve strategy

  #3386 opened 8 months ago by char0n
  1

• Consolidate code for HTTP client

  #3481 opened 8 months ago by glowcloud
  1

• resolver: align OpenAPI 3.1.0 resolver implementation with latest ApiDOM

  #3467 opened 8 months ago by char0n
  1

• Rework encodeDisallowedCharacters function for OpenAPI 3.x request builders

  #3462 opened 9 months ago by glowcloud
  1

• resolver: utilize ApiDOM's async plugins dispatcher and visitor merger

  #3455 opened 9 months ago by char0n
  2

• Feature Request: Access response body for Error responses

  #3440 opened 9 months ago by SeanLMcCullough
  0

• OpenAPI 2.x: undefined body and path parameters are included in requests

  #3438 opened 9 months ago by glowcloud
  1

• OpenAPI 2.x: make execute parameter builders for query and formData consistent with each other

  #3436 opened 9 months ago by glowcloud
  1

• OpenAPI 2.x: execute builder for formData parameter should not skip falsy values

  #3434 opened 9 months ago by glowcloud
  1

• Integrate ApiDOM@0.98.0

  #3430 opened 9 months ago by char0n
  1

• Traversal of large spec broken after #3380

  #3385 opened 10 months ago by am-burban
  5

• Is there something missing in supporting OAS3 servers?

  #3143 opened a year ago by fulviodenza
  9

• unidici security issue

  #3382 opened 10 months ago by char0n
  1

• Integrate ApiDOM@0.90.0

  #3311 opened a year ago by char0n
  2

• When i update to 2.23.0 ,build failed

  #3176 opened a year ago by KingDracula
  5

• Switching from node 16 to 18 changes TLS implementation of request on spec

  #3163 opened a year ago by dchicchon
  3

• Set client/server TLS options

  #3144 opened a year ago by tomchiverton
  2

• Integrate swagger-js with latest ApiDOM

  #3171 opened a year ago by char0n
  1

• Cookie Auth not working while sending req through different port then server.

  #3167 opened a year ago by VijayRathod20
  1

• abort controller doesn't abort requests (Tags feature)

  #3168 opened a year ago by cjenkscybercom
  0

• swagger-client@3.22.2: `absolutifyPointer` returns `[ERR_INVALID_URL]: Invalid URL` on Windows

  #3149 opened a year ago by AlvaroRausell
  5

• Introduce backward compatible URI Reference resolution

  #3147 opened a year ago by char0n
  3

• Allow to set http.Agent

  #3032 opened a year ago by linhx
  4

• Feature to configure accept-header for config file requests

  #3140 opened a year ago by 2WeltenChris
  1

• Check Node.js 18 and 20 on CI

  #3114 opened a year ago by pvcresin
  4

• @swagger-api/apidom-core@0.76.0 requires node 15 or greater, breaks Node-14 CI

  #3127 opened a year ago by shazron
  4

• swagger-bot gone awry: node-14 tests failed but it wants the PR to still be merged

  #3126 opened a year ago by shazron
  1

• Error resolving open api spec with circular dependency

  #3063 opened a year ago by mikewang333
  2