fix: flag eval snap name#345
Merged
Merged
Conversation
agrognetti
approved these changes
Jan 14, 2026
Merged
abelonogov-ld
pushed a commit
that referenced
this pull request
Jan 16, 2026
🤖 I have created a release *beep* *boop* --- <details><summary>launchdarkly-observability-android: 0.23.1</summary> ## [0.23.1](launchdarkly-observability-android-0.23.0...launchdarkly-observability-android-0.23.1) (2026-01-16) ### Bug Fixes * flag eval snap name ([#345](#345)) ([f10980e](f10980e)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Publishes `sdk/@launchdarkly/observability-android` 0.23.1. > > - CHANGELOG adds bug fix: flag eval snap name > - Updates `.release-please-manifest.json` and `gradle.properties` version to `0.23.1` > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 3dcf918. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY -->
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
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.
Summary
Fix flag eval name
How did you test this change?
Are there any deployment considerations?
Note
Aligns feature flag evaluation tracing with consistent span naming and attribute/event semantics.
FEATURE_FLAG_SPAN_NAME(evaluation) for flag evaluation spans and attachfeature_flag.key,feature_flag.provider.name, andfeature_flag.context.idon creationfeature_flagevent on the captured evaluation span with optional value, variation index, and in-experiment reason; then end the spanflagKeyset to"my-feature"inMainActivity.ktWritten by Cursor Bugbot for commit dd3d9cb. This will update automatically on new commits. Configure here.