Does anyone know why Android Studio adds the fully...

# android-studio

[Zoltan Demant]

Does anyone know why Android Studio adds the fully qualified name for certain composables (this seems to happen particularly often for design.component.* in my case)? It even suggests removing it, but seems odd that I need to do that for every composable when I know better ways to spend my time 🤷🏽‍♂️

[Zoltan Demant]

If I type Text("abc") it will add the fully qualified name like in the screenshot above. If I then add another Text("xyz") right next to it, the same thing happens again.

[sindrenm]

Yeah, it happens fairly often for me, too, and not just for our own things, but also for Compose library composables and types. It appears to me that it only happens when there are multiple matching names. Just today I autocompleted SharedTransitionScope , and it both spelled out the fully qualified name of androidx.compose.animation.SharedTransitionScope, and added an import for it.

androidx.compose.animation.SharedTransitionScope exists both as a composable and as a class.

[Zoltan Demant]

Hmm, I wonder if its specifically related to the 1+ match thing you mention. I first dismissed it because I can recreate the issue with almost any composable, i.e. Scaffold. The Scaffold lives in design.component.Scaffold and its the only suggestion that pops up, but the IDE might be "aware" of the M3 scaffold (which the design system scaffold uses under the hood) and hence causing the issue. If I use a very unique composable, I dont run into this. Might be worth filing an issue, Ill do it next week (pretty swamped right now 😃)