-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Module name, type name aliasing conflict #396
Comments
Thanks for opening this issue!
|
What exactly are you trying to do? For example what code isn’t compiling and how does it differ from the many tests in the test suite? Heres an example using combine: Parse-Swift/Tests/ParseSwiftTests/ParseLiveQueryCombineTests.swift Lines 43 to 69 in a143c0f
Another using Subscription: https://github.com/netreconlab/SnapCat/blob/66bd9a2cecd4e665bc7bca13ce74690d2c613bb2/SnapCat/CustomViewModels/QueryImageViewModel.swift#L14-L340 |
I was trying to use an It fails anyways even if I use In your examples you do not use Anyways there's a reason why there's no |
Thanks for reporting and describing your issue. The linked PR should address the problem |
Thank you for the quick response and for working on the library! |
New Issue Checklist
Issue Description
ParseSwift
module is named the same as theParseSwift
class, that makes it impossible to write a fully qualified type in case of the naming conflict. AndParseSwift.Subscription
already has a conflict withCombine.Subscription
.Steps to reproduce
This means I cannot even specify
EnvironmentObject
:If the module name was different from the class name it could be possible to have
Maybe another option is to have typealiases for conflicting names but it doesn't resolve conflicts with local project names.
AFAIK there's no tool like
::
in Swift. The only way I see it can be fixed now by the library user is by importing and aliasing specific types fromCombine
, and never importCombine
when I want to useSubscription
. Like this:Actual Outcome
Errors
Expected Outcome
No errors
Environment
Client
4.9.0
13.4.1 (13F100)
Logs
n/a
The text was updated successfully, but these errors were encountered: