You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Obj-C SentryUser has a Swift name of User via NS_SWIFT_NAME(User). User is an incredibly common class name in apps, and having this renamed to User in Swift causes a lot more issues than it needs to. If I have a class that uses both Sentry and my own User class, I need to explicitly use MyModule.User in order to avoid naming conflicts.
I understand this would be a breaking change, but using the Sentry framework should provide as few roadblocks to using our own code as possible. Thanks!
The text was updated successfully, but these errors were encountered:
Ah, if you just opened up this issue a few days earlier 😁. We just shipped 7.0.0. I add this to 8.0.0, so we can discuss this in the next major. I agree with you that we should change this. Thanks for pointing it out.
The Obj-C
SentryUser
has a Swift name ofUser
viaNS_SWIFT_NAME(User)
.User
is an incredibly common class name in apps, and having this renamed toUser
in Swift causes a lot more issues than it needs to. If I have a class that uses both Sentry and my ownUser
class, I need to explicitly useMyModule.User
in order to avoid naming conflicts.I understand this would be a breaking change, but using the Sentry framework should provide as few roadblocks to using our own code as possible. Thanks!
The text was updated successfully, but these errors were encountered: