Improve automatic tagging of Composables
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the compiler plugin implementation and the linked VKCOM TestTagApplier prior art to understand how composable names become SentryTag values. Done means automatic tags uniquely distinguish composables using the proposed source details and ViewHierarchies and Transactions represent the traced components more accurately.
Written by the indexing model from the issue text.
Description
Description
Currently our automatic tagging through the compiler plugin is suboptimal, because we're using a Composable name for SentryTag which can be default composable names like Image/Text/Slider etc. and which don't uniquely identify the composable.
We could use filename + function name + lineno to uniquely identify composables and make the ViewHierarchies and Transactions better represent what components are being traced.
- Dominant language
- Kotlin
- Stars
- 184
- Forks
- 41
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 19
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getsentry/sentry-android-gradle-plugin
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getsentry/sentry-android-gradle-plugin#1454 · 1 comment ·
Maintainers usually reply within 1 day
-
Android Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
getsentry/sentry-android-gradle-plugin#1369 · 1 comment ·
Maintainers usually reply within 1 day
-
Android good first issue Improvement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getsentry/sentry-android-gradle-plugin#1266 · 1 comment ·
Maintainers usually reply within 1 day
-
Android Feature Stale Waiting for: Community
Difficulty 4/5 3-5 days Newbie friendliness 45/100
getsentry/sentry-android-gradle-plugin#1406 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Task
Difficulty 4/5 3-5 days Newbie friendliness 45/100
getsentry/sentry-android-gradle-plugin#1354 · 1 comment ·
Maintainers usually reply within 1 day
All issues in getsentry/sentry-android-gradle-plugin
Similar issues
-
Source is down
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
keiyoushi/extensions-source#19491 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
MTES-MCT/rapportnav2#1557 ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
emm3000/Just-Chill#543 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vaadin/intellij-plugin#600 ·
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 65/100