Clarify Pixel-Image relationships as 1-1#38
Merged
stellarsunset merged 1 commit intomainfrom Dec 21, 2025
Merged
Conversation
…ct this to be 1-1
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #38 +/- ##
=========================================
Coverage 73.62% 73.62%
+ Complexity 233 232 -1
=========================================
Files 72 71 -1
Lines 1638 1638
Branches 188 188
=========================================
Hits 1206 1206
Misses 342 342
Partials 90 90 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
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.
Move the Pixel sub-classes into their associated image types to clarify all concrete image types are generally expected to have their own semantically meaningful pixel handle.