-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
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
fix(client-cli): Properly interpret nullable prop #1938
fix(client-cli): Properly interpret nullable prop #1938
Conversation
Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Slap a |
Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com>
Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com>
Signed-off-by: Roberto Bianchi <roberto.bianchi@spendesk.com>
@mcollina not sure it's related to coverage 🤔 So I'm not sure it's related to this PR to be honest |
@@ -400,6 +400,7 @@ async function plugin (app, opts) { | |||
client = await buildOpenAPIClient(opts, app.openTelemetry) | |||
} else if (opts.type === 'graphql') { | |||
if (!opts.url.endsWith('/graphql')) { | |||
/* c8 ignore next 2 */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI @mcollina probably this can be removed in another PR 😉
With this change, when an Open API schema contains a
nullable: true
property, it's properly handled and the generated type will contain| null;