Repository navigation
Conversation
apify-service-account
added
the
t-tooling
Contributor
|
✅ Preview for this PR (commit |
Contributor
|
API behavior and specification alignment: Aligned. |
Contributor
|
Can you also explain the circumstances under which the buildId is null in the spec? |
Member
Author
Not 
|
Contributor
I mistyped, sorry. I didn't mean for you to explain it to me, but to include the explanation in the spec. |
This branch has not been deployed
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
3 participants
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.
A build made from a version without a build tag returns
actVersion.buildTag: null(e.g.GET /v2/actor-builds/Y5XdRkw2aS83tQrXG), so this makes it nullable likebuildTaginVersion.yaml, which apify-client-js currently rejects with aResponseValidationError.