-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
'View' is ambiguous for type lookup in this context #1305
Comments
It is the cost to maintain the semantic version. To resolve it, you can only import the type you need from Kingfisher instead of importing all. Like: import class Kingfisher.KingfisherManager |
ok, thank you for your quick reply. By the way, is there a plan to release Kingfisher 6.0? |
Not that soon. |
Hi, I don't quite understand what to do here. Was not having any issues until the latest release. For instance, Im just using KFImage and Get the same 'View' is ambiguous for type lookup in this context. Basically I: import SwiftUI How would I import Kingfisher now? |
Just figured something out. When using CocoaPods, I could figure out how to import. But when using SPM I can just import with KingfisherSwiftUI and everything works fine. |
Yes. If you only use types from |
Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.
Issue Description
What
#1304 introduce some public type alias which conflict with some components in SwiftUI (View, Color and Button). As a result, any file in host app who imports both Kingfisher and SwiftUI, needs to add module name before those basic SwiftUI components, which leads to inconvenience.
Reproduce
Other Comment
Is there workaroud to this issue? Thanks.
The text was updated successfully, but these errors were encountered: