Skip to content
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

refactor: rename native options #2940

Merged
merged 7 commits into from
Dec 4, 2023
Merged

refactor: rename native options #2940

merged 7 commits into from
Dec 4, 2023

Conversation

vaind
Copy link
Collaborator

@vaind vaind commented Dec 3, 2023

closes #2934

@vaind vaind marked this pull request as ready for review December 3, 2023 14:31

#### Changed APIs

- Rename iOS and MacCatalyst platform specific options from `Cocoa` to `Native` ([#2940](https://github.com/getsentry/sentry-dotnet/pull/2940))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note to final 4.0.0 changelog rewording: outside the beta there was no Cocoa, it was iOS to Native (right?)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and that is also true for many other parts of the 4.0 changelog. we need to update it and review thoroughly before the final release.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could keep track of these things in a ticket (we already have #2673)?

@@ -9,17 +9,17 @@ internal class AndroidEventProcessor : ISentryEventProcessor, IDisposable
private readonly JavaSdk.IEventProcessor? _androidProcessor;
private readonly JavaSdk.Hint _hint = new();

public AndroidEventProcessor(SentryAndroidOptions androidOptions)
public AndroidEventProcessor(SentryAndroidOptions nativeOptions)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should class SentryAndroidOptions also become SentryNativeOptions or that's rather confusing because sentry-native?

Although I see it being renamed below, did we have 2 SentryAndroidOptionss?

Copy link
Collaborator Author

@vaind vaind Dec 3, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This refers to Java class name

@@ -6,7 +6,7 @@

<ItemGroup>
<Using Include="Foundation" />
<Using Include="Sentry.CocoaSdk.SentryOptions" Alias="SentryCocoaOptions" />
<Using Include="Sentry.CocoaSdk.SentryOptions" Alias="SentryCocoaSdkOptions" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about?

Suggested change
<Using Include="Sentry.CocoaSdk.SentryOptions" Alias="SentryCocoaSdkOptions" />
<Using Include="Sentry.CocoaSdk.SentryOptions" Alias="SentryCocoaOptions" />

Not sure the namespace is CocoaSdk, could it be Cocoa? Do we call JavaSdk or AndroidSdk on the other binding?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is related to the native cocoa SDK generated binding code. I didn't want to touch that internal bit

@vaind vaind merged commit a2fa21f into main Dec 4, 2023
20 checks passed
@vaind vaind deleted the refactor/native-options-rename branch December 4, 2023 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Native iOS/Cocoa options naming - 4.0.0-beta.3
3 participants