Fix: Fix API Parameter Type Bug Causing Undefined Error and Unintended Required Status

[JSYOU]

Description

This PR addresses a bug in the API definition file where specifying a parameter type would cause an error when the parameter was undefined, indirectly making it required.
The fix ensures that specifying a type for a parameter no longer affects its required status.

Issue ticket number

N/A

Additional Context

urlPath: /artist/:id
request:
  - fieldName: id
    fieldIn: path
    description: constituent id
    validators:
      - required
  - fieldName: begin_date
    fieldIn: query
    type: number
    description: begin date
    validators:
      - date
sample:
  parameters:
    id: '1'
  profile: duckdb
profile: duckdb

before:

after:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vulcan-sql-document	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 14, 2023 4:15pm

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Files	Coverage Δ
...ckages/core/src/lib/utils/normalizedStringValue.ts	95.83% <100.00%> (+0.59%)	⬆️
...alidators/built-in-validators/dateTypeValidator.ts	90.47% <0.00%> (-4.53%)	⬇️

... and 1 file with indirect coverage changes

📢 Thoughts on this report? Let us know!.

[kokokuo]

Hi @JSYOU,

Looks like you only solved one scenario for giving the type number, but when the user does not provide the type field, it happens when the schema.yaml created from Canner enterprise data service like the below source:

# schema

urlPath: /artist/:id
request:
  - fieldName: id
    fieldIn: path
    description: constituent id
    validators:
      - required
  - fieldName: begin_date
    fieldIn: query
    description: begin date
    validators:
      - name: date
        args:
          format: YYYY-MM-DD
sample:
  # parameters:
  #   id: '1'
  # profile: duckdb
profile: duckdb

and the sql file

select 
*
from "artists"
where
ConstituentID = {{ context.params.id }}
{% if contex.params.begin_date %}
    and BeginDate = {{ context.params.begin_date }}
{% endif %}

PS: The code generated from the labs/playground package's artists but little changed schema.yaml

it still happens the error:

The input parameter is invalid, it should be date type

[kokokuo]

LGTM 👍

[kokokuo]

Only date validator needs to add the checker, and the integer, uuid, and string of the validator work, so it does not need to add the undefined checker.