-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Ambiguous reference error occurs when other package is included that provides its own Color object #1331
Comments
There's nothing we can do in the .NET MAUI Community Toolkit to resolve the fact that ImageSharp and .NET MAUI both have a class named We don't control either of those repositories. |
Apologies. I understand now that it is our Source Generator generating code causing the naming conflict. Thanks for the PR! |
The workaround is to create a
|
The workaround doesn't work. I need the exact opposite. Is this still present in the latest 7.0.0 package? |
There is a new assignment of a transparent color to "element.Color", do you prefer if I create new issue for the new PR? line 36 of the generate file: EDIT; it is referring to a class |
@IIARROWS Here's a couple GitHub pro-tips to help you know what has been merged and what hasn't:
To answer you question, this bug fix has been included in |
Is there an existing issue for this?
Did you read the "Reporting a bug" section on Contributing file?
Current Behavior
When creating a new MAUI project and adding MAUI Community Tookit and another project that includes its own Color object (e.g. SixLabors.ImageSharp, the following error occurs:
Expected Behavior
No error should occur.
Steps To Reproduce
Link to public reproduction project repository
https://github.com/wolfgang-ironsoftware/MauiCommunityToolkitColorIssue
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: