Support the use of string or number via $ref in path parameters

[hadashiA]

Types of changes

• Bug fixes
  • resolves #
• Features
  • resolves #
• Maintenance
• Documentation

Changes

• Support the use of custom types in path parameters if type is actually alias of string or number.

Additional context

Currently, only number or string can be used for the path parameters.

( This is validation on the side of aspida/aspida. https://github.com/aspida/aspida/blob/main/packages/aspida/src/createTemplateValues.ts#L9 )

In openapi2aspida, even if it is a string or a number, an error will occur if a $ref reference is interposed.

In my use case, I want to define the path parameter string as follows:

paths:
  "/invoices/{invoiceCategory}":
    get:
      parameters:
      - name: invoiceCategory
        in: path
        required: true
        schema:
          "$ref": "#/components/schemas/InvoiceCategory"
components:
  schemas:
    InvoiceCategory:
      type: string
      enum: ["category-1", "category-2"]

openapi2aspida does not know that "$ref": "#/components/schemas/InvoiceCategory" is actually a string.

└── invoices/
    └── [email protected]

Therefore,

Error: aspida ERROR '[email protected]' does not match '/^_[a-zA-Z][a-zA-Z0-9_]*(@number|@string)?((\.|%[0-9a-fA-F]{2})[a-zA-Z0-9]+)?$/'.
    at /Users/hadashi/src/github.com/aspida/openapi2aspida/node_modules/aspida/dist/createTemplateValues.js:42:27
    at Array.map (<anonymous>)
    at createApiString 
...

So, in this PR, I added a process to check the destination of $ref and fallback if it is a simple string type.

Community note

Please upvote with reacting as 👍 to express your agreement.