We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
oneOf
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
Hi! Looks like any field with an empty oneOf is causing the script to error out with a syntax error: error: SyntaxError: '=>' expected
error: SyntaxError: '=>' expected
In my specific case, it's
SyntaxError: '=>' expected. (237:16) 235 | 236 | }; > 237 | "MetaQuote": ();
In the input file, MetaQuote is defined as:
MetaQuote
MetaQuote: oneOf: [] discriminator: propertyName: meta_serialization_key mapping: {}
Only after I removed all fields with an empty oneOf did the script stop erroring out.
It may be similar to #561, where the fix was made for empty enums.
enum
The text was updated successfully, but these errors were encountered:
Start working on it. So what's the expected result of oneOf: [] and allOf: []? Is it undefined, @deannashih?
oneOf: []
allOf: []
undefined
Also it's can be any or unknown, but I prefer undefined for stronger typing.
any
unknown
Got this result:
UPD: #830
Sorry, something went wrong.
@drwpow @sadfsdfdsa Looks like this issue re-emerged in v5.2.0. Was working in 5.1.0.
I believe this was fixed in #1069 for version 6. Previously, this schema generated like so:
MetaQuote: ;
but now generates as:
MetaQuote: never;
Comment here if different behavior is desired.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Hi! Looks like any field with an empty
oneOf
is causing the script to error out with a syntax error:error: SyntaxError: '=>' expected
In my specific case, it's
In the input file,
MetaQuote
is defined as:Only after I removed all fields with an empty
oneOf
did the script stop erroring out.It may be similar to #561, where the fix was made for empty
enum
s.The text was updated successfully, but these errors were encountered: