You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wanting to add a customformat destination namespace but the current POST request requires the full syncCatalog included in its schema instead of referencing existing.
Describe the solution you’d like
I would like a PATCH request that simply takes the following schema:
I tried to look into this and would happy to submit a PR, but would definitely need some pointers on how to start e.g. a blueprint of what the patch request would look like.
The text was updated successfully, but these errors were encountered:
Tell us about the problem you're trying to solve
I am wanting to add a customformat destination namespace but the current POST request requires the full
syncCatalog
included in its schema instead of referencing existing.Describe the solution you’d like
I would like a PATCH request that simply takes the following schema:
Describe the alternative you’ve considered or used
I looked into adding this simply PATCH path in the openapi config.yaml but it's proving somewhat difficult given the way it's structured.
This approach DRY up the PATCH <- POST <- GET inheritance chain looks extremely appealing regarding this issue however I imagine that's a significant overhaul of the inherent API structure.
Additional context
OAI/OpenAPI-Specification#2201
Are you willing to submit a PR?
I tried to look into this and would happy to submit a PR, but would definitely need some pointers on how to start e.g. a blueprint of what the patch request would look like.
The text was updated successfully, but these errors were encountered: