airtasker#1417 @oaSchemaProp example fails with numerical strings, Date, DateTime, Object, Array, Union or Intersection #1419
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description, Motivation and Context
Please see #1417
When using
@oaSchemaProp example
, providing a numerical string like "123.3" for a String type fails.When using
@oaSchemaProp example
forDate
,DateTime
, Object, Array, Union or Intersection type it fails.Fix in this PR :
in
function extractJSDocSchemaProps(
const typeOf
is refactored and will use theJSON.parse
real type instead of regexp filtering.Checklist: