Fix dereferencing in Function and AsyncFunction#440
Merged
Conversation
We were accidentally stripping out all components in the schemas due to the Input/Output being referenced by PredictionRequest and PredictionResponse and those in turn being referenced by the various `path` entries. This commit ensures we retain Input and Output and cleans up the object to only contain relevant fields.
aron
changed the title
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 were accidentally stripping out all components in the schemas due to
the Input/Output being referenced by PredictionRequest and
PredictionResponse and those in turn being referenced by the various
pathentries. This commit ensures we retain Input and Output andcleans up the object to only contain relevant fields.