We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The types of the components are always assumed to be object. Generally, enums are allowed to be components and they can have integer or string types.
Example enum component:
"SomeType":{"title":"SomeType","enum":["TYPE_1","TYPE_2","TYPE_3"],"type":"string","description":"An enumeration."}
Assumption is made here in transforms/components/index.js (line 82 -> type:'object')
transforms/components/index.js
type:'object'
return { [typedef.name]: { ...combineSchema(elements), description: schema.description, ...(requiredProperties.length ? { required: formatRequiredProperties(requiredProperties), } : {}), type: 'object', properties: formatProperties(propertyValues, options), }, };
Would be great if @typedef {string} creates a string type
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The types of the components are always assumed to be object. Generally, enums are allowed to be components and they can have integer or string types.
Example enum component:
Assumption is made here in
transforms/components/index.js
(line 82 ->type:'object'
)Would be great if @typedef {string} creates a string type
The text was updated successfully, but these errors were encountered: