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

feat(editor-content-type): use OpenAPI 2.0 ApiDOM parser adapters for detection #4530

Merged
merged 1 commit into from
Nov 1, 2023

Conversation

char0n
Copy link
Member

@char0n char0n commented Nov 1, 2023

Refs swagger-api/apidom#389


Instead of maintaining the fragile resolve aliases,
npm overrides package.json field will be used
to avoid double-bundling different versions of ApiDOM.

@char0n char0n self-assigned this Nov 1, 2023
@char0n char0n merged commit 989a51a into next Nov 1, 2023
2 checks passed
@char0n char0n deleted the char0n/openapi-2-parser-adapters branch November 1, 2023 13:55
swagger-bot pushed a commit that referenced this pull request Nov 1, 2023
# [5.0.0-alpha.79](v5.0.0-alpha.78...v5.0.0-alpha.79) (2023-11-01)

### Features

* **content-type:** use OpenAPI 2.0 ApiDOM parser adapters ([#4530](#4530)) ([989a51a](989a51a))
@swagger-bot
Copy link
Contributor

🎉 This PR is included in version 5.0.0-alpha.79 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants