Cover ProjectConnectionPayload's metadata branch (100% coverage gate) - #6
Merged
Merged
Conversation
CI's 100% coverage gate caught it: toAzureBody()'s metadata !== [] branch had no test passing non-empty metadata, only the default empty array.
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.
Follow-up to #5, which merged before this fix landed on the PR branch — main currently has the project-connections feature at 99.9% coverage (the `metadata !== []` branch in `ProjectConnectionPayload::toAzureBody()` had no test), so `composer test:coverage`'s 100% gate is red on main right now.
This is the exact fix pushed to #5's branch after it merged: one added test case exercising non-empty metadata.
🤖 Generated with Claude Code