Skip to content
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: component extension merge #270

Merged
merged 1 commit into from
Feb 7, 2023
Merged

Conversation

jlourenc
Copy link
Contributor

@jlourenc jlourenc commented Feb 7, 2023

PR #269 introduces a bug with the upgrade of kin-openapi. Component extensions are not correctly identified and considered as part of merging specs. However, a nil pointer exception can occur when no extensions are specified as part of a spec.

This PR correctly handles this nil pointer and add tests to validate behaviour.

@jlourenc jlourenc requested a review from a team as a code owner February 7, 2023 11:33
PR #269 introduces a bug with the upgrade of kin-openapi. Component
extensions are not correctly identified and considered as part of
merging specs. However, a nil pointer exception can occur when no
extensions are specified as part of a spec.

This PR correctly handles this nil pointer and add tests to validate
behaviour.
@jlourenc jlourenc force-pushed the fix/component-extension-merge branch from d74dcb8 to a93a544 Compare February 7, 2023 11:36
@jlourenc jlourenc merged commit 29347e2 into main Feb 7, 2023
@jlourenc jlourenc deleted the fix/component-extension-merge branch February 7, 2023 11:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants