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: optional use of meta patches in swagger-client dereference strategy #2336

Closed
Tracked by #2289
char0n opened this issue Dec 6, 2022 · 0 comments
Closed
Tracked by #2289

apidom-reference: optional use of meta patches in swagger-client dereference strategy #2336

char0n opened this issue Dec 6, 2022 · 0 comments
Assignees
@char0n
Labels
ApiDOM enhancement New feature or request OpenAPI 3.1

Comments

@char0n
Copy link
Member

char0n commented Dec 6, 2022

Goal of this issue is to introduce support for meta patches in swagger-client dereference strategy.

When allowMetaPatches=true - decorate referenced structure with $$ref field and assign it an absolutified JSON Pointer.

Refs #2289
@char0n char0n mentioned this issue Dec 6, 2022
Closed
5 tasks
@char0n char0n self-assigned this Dec 6, 2022
@char0n char0n added enhancement New feature or request OpenAPI 3.1 ApiDOM labels Dec 6, 2022
char0n added a commit that referenced this issue Dec 6, 2022
@char0n
feat(reference): add support for allowMetaPatches option
d45400a 
This affects OpenAPI 3.1 swagger-client dereference strategy.

Refs #2336
@char0n char0n mentioned this issue Dec 6, 2022
Merged
char0n added a commit that referenced this issue Dec 6, 2022
@char0n
feat(reference): add support for allowMetaPatches option (#2337)
22c5c7c 
This affects OpenAPI 3.1 swagger-client dereference strategy.

Refs #2336
@char0n char0n closed this as completed Dec 6, 2022
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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@char0n