Resolve ambiguity for Color with named imports #670
Merged
Conversation
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
Resolves an import ambiguity by specifying `ComposeColor` and `AndroidColor` type aliases in the Imagen snippets. This change also cleans up unused imports and alphabetizes the remaining ones.
calren
approved these changes
Oct 23, 2025
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.
Resolves an import ambiguity by specifying
ComposeColorandAndroidColortype aliases in the Imagen snippets. This change also cleans up unused imports and alphabetizes the remaining ones.These snippets use multiple "Color" classes so we need named imports to distinguish them. Here is the current documentation. I can't put region tags around the imports because Android Studio and Spotless will reorder the comments and break the inclusion regions. I think a comment is a reasonable solution to show the imports.
Documentation page: