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.

Sign up for GitHub

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

Jump to bottom

apidom-reference: create OpenAPI 3.1 YAML 1.2 parsing adapter compatible with swagger-client #2324

Closed
char0n opened this issue Dec 1, 2022 · 0 comments
Closed

apidom-reference: create OpenAPI 3.1 YAML 1.2 parsing adapter compatible with swagger-client #2324

char0n opened this issue Dec 1, 2022 · 0 comments
Assignees
@char0n
Labels
ApiDOM enhancement New feature or request OpenAPI 3.1 tests tag for anything test related YAML

Comments

@char0n
Copy link
Member

char0n commented Dec 1, 2022

The goal of this issue to create OpenAPI 3.1 YAML 1.2 parsing adapter capable of parsing semantic OpenAPI 3.1 YAML in the same way as swagger-client does it.
@char0n char0n self-assigned this Dec 1, 2022
@char0n char0n added enhancement New feature or request ApiDOM YAML tests tag for anything test related OpenAPI 3.1 labels Dec 1, 2022
char0n added a commit that referenced this issue Dec 1, 2022
@char0n
test(reference): add swagger-client OpenAPI 3.1 YAML parser plugin
25101f5 
This plugin mimics the YAML parsing mechanism from swagger-client.

Refs #2324
@char0n char0n mentioned this issue Dec 1, 2022
Merged
@char0n char0n closed this as completed Dec 1, 2022
char0n added a commit that referenced this issue Dec 1, 2022
@char0n
test(reference): add swagger-client OpenAPI 3.1 YAML parser plugin (#…
a93b820 
…2325)

This plugin mimics the YAML parsing mechanism from swagger-client.

Refs #2324
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@char0n char0n

Labels
ApiDOM enhancement New feature or request OpenAPI 3.1 tests tag for anything test related YAML
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@char0n