[Bitbucket Datacenter] Return empty list instead of null #4010
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
qwerty287
added
forge/bitbucket
qwerty287
approved these changes
Aug 6, 2024
|
@jenrik please update your branch |
lafriks
approved these changes
Aug 6, 2024
jenrik
force-pushed
the
fix/bitbucket-array-init
branch
from
42ec9d0 to
6ff8419
Compare
|
@qwerty287 rebase completed |
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 change make the Bitbucket Datacenter forge correctly return empty list instead of nil which indirectly fixes the "Run pipeline" button in the repository view.
Previously you where unable to manually run a pipeline because the frontend code expects the API to return a empty JSON array for the last page instead of the null value that where actually returned.