fix(api): fix incorrect I2I OpenAPI gateway spec #105
Merged
Conversation
This file contains 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
This commit ensures that the right format is set in the OpenAPI spec for when the I2I response is coming from the gateway. This is a little bit hacky since we don't yet generate the OpenAPI spec where it is implemented (i.e. in go-livepeer).
rickstaa
force-pushed
the
fix_I2I_gateway_spec
branch
from
1c93591
to
a0d3e9d
Compare
eliteprox
pushed a commit
to eliteprox/ai-worker
that referenced
this pull request
Jul 26, 2024
This commit ensures that the right format is set in the OpenAPI spec for when the I2I response is coming from the gateway. This is a little bit hacky since we don't yet generate the OpenAPI spec where it is implemented (i.e. in go-livepeer).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request ensures that the right format is set in the OpenAPI spec forwhen the I2I response is coming from the gateway. This is a little bit hacky since we don't yet generate the OpenAPI spec where it is implemented (i.e. in go-livepeer).