Allow SDK consumers to specify release name #285
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
crazytonyli
approved these changes
Mar 26, 2024
wzieba
commented
Mar 28, 2024
| options.environment = self.dataProvider.buildType | ||
| switch self.dataProvider.releaseName { | ||
| case .setByApplication(let name): options.releaseName = name | ||
| case .setByTracksLibrary: options.releaseName = nil |
Member
Author
There was a problem hiding this comment.
Leaving a breadcrumb: this is bug (addressed in Android in: Automattic/Automattic-Tracks-Android#209)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Twin PR for Android: Automattic/Automattic-Tracks-Android#206
Description
Allow SDK consumers to specify release name or that it wants to delegate setting up release name to SDK (it's by default).
Why?
We would like to decrease a number of "fake releases" (created by running an up from e.g. PR build) to maek Sentry dashboard easier to navigate in. E.g., these highlighted releases are "fake" ones:
CHANGELOG.mdif necessary.