Swagger node is taking URL phrase as parameter

Question

I'm using swagger-node for REST APIs and I've found an absurd issue here.

Here's my one of GET requests:

GET: /students/{id}/{name}

(id is number)

And now I wrote another request:

GET: /students/routeInfo/{id}

But the 2nd request me following error:

Expected type is number, found type string. Which clearly means 2nd request is trying to "mask" 1st request. Which I think shouldn't be.

Am I doing something wrong or is there any other way to handle this?

score 0 · Answer 1 · answered Dec 06 '17 at 19:38

0

In your path definitions, changeChange your 'parameters' type: number for type: string

Your path will look like this:

/students/routeInfo/{id}:
x-swagger-router-controller: yourStudentController
get:
  tags: 
    - Student
  description: description
  operationId: yourOperation
  parameters:
    - name: id
      in: path
      description: description id of routeInfo 
      required: true
      type: string

See more at https://swagger.io/docs/specification/paths-and-operations/

answered Dec 06 '17 at 19:38

SebaReal

161
2
7

Please remove or edit your answer. You need to learn more about swagger and `type` keyword. This won't solve the problem. You clearly didn't understand the question. – Vikas Dec 07 '17 at 02:08

score 0 · Answer 2 · answered Dec 07 '17 at 10:49

The exact same situation is described in the OpenAPI specification v3.0 document: section Path Templating Matching, 3rd example. It is called ambiguous matching, and "... it's up to the tooling to decide which path to use." The tool, of course, being swagger-node.

It is weird though, isn't it!

Swagger node is taking URL phrase as parameter

2 Answers2