Fix Issues in Platform Swagger Specs #32
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've just gone through the process of generating an AEP client from the swagger spec and in doing so, we encountered many issues where the specs diverged from the reality of the API, or they were missing important pieces of information required to generate a working client.
There will likely be further issues, but I feel like we've now solved all those relating to the most common data ingestion use cases (creating datasets, field groups, schemas, connections, dataflows), so it seems like a good time to raise a PR.
Please let me know if you'd like any further explanation for the changes made.