chore(compose): Rename file for SentryTraced - #6059
Open
0xadam-brown wants to merge 1 commit into
Open
Conversation
Note: Rename keeps binary compatibility with previous file name for Java clients.
0xadam-brown
requested review from
adinauer,
markushi,
romtsn and
runningcode
as code owners
September 5, 2026 15:07
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.
📜 Description
Renamed
SentryComposeTracing.kt->SentryTraced.ktto match our usual conventions + make it easier to find SentryTraced in the IDE.Rename keeps binary compatibility with previous file name for Java clients.
💡 Motivation and Context
Having file names match public composable APIs is especially helpful b/c composables are functions, not classes, so most IDEs don't have a type-based global search for them (but do let you search files by name).
💚 How did you test it?
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps
#skip-changelog