Stylianos Gakis

01/04/2022, 1:46 PM
There’s one tooling “problem” (might just be me) with compose that I haven’t seen people discuss yet. When we do “Search usages” (Cmd/Ctrl + B) on a composable function, we get both references to it inside @Preview composable functions and in production code. I kind of wish there was a way to filter out the usages inside the previews because like 99% of the time it is not what I am looking for, and it only makes it so much slower to go into the production versions of them. It’s especially annoying that by default the pre-selected option that comes when clicking the shortcut is sometimes the preview one, and sometimes the production one. So it’s not consistent, making every time I click it a mini-game of me trying to figure read which one has the “Preview” suffix (picture attached). Does anyone else feel the same way? Any ideas to make this mild annoyance nicer?
Bringing attention to this again, not sure if it’s really a big deal only for me somehow 😅 I don’t know why I haven’t seen literally anyone else mention this? I don’t know what the solution might be either. A minimum would be to at least have a consistent order in which they come in, maybe in a configurable way somehow or if not always have the @Preview functions come last. Optimally a filter for @Previews just like I always use the one for imports would exist, but maybe that’d be weird to integrate in the IDE when composables isn’t something that everyone is using. But someone smarter than me maybe can have a more creative solution?
☝️🏼 1


03/07/2022, 9:35 PM
I think it'd make sense to submit a feature request on

Stylianos Gakis

03/07/2022, 9:38 PM
I haven’t done so so far because I don’t know what to suggest. I know I am annoyed by it, but if I just make a feature request with my complaint it helps nobody. I might just write basically what I wrote in this message, with my random ideas and go from there, see if anyone from inside Google has had this on their mind as well! Thanks btw Louis 🙌

Bryan Herbst

03/07/2022, 9:46 PM
There’s nothing stopping an
Composable from also being production code.

Stylianos Gakis

03/07/2022, 9:50 PM
That is true, and I am aware of it which only makes a possible solution to this even more complicated. Practically, in the code that I’ve been working on I’ve never found a case where I’ve done that, since most composables take inputs and then you depend on the callers to fill them, but regardless, I am sure some people use it that way and it’d be hard to account for them as well.
Created this Please do chime in if you have opinions on this!

Adam Powell

03/07/2022, 10:16 PM
added @Chris Sinco [G] to it 🙂
👍 1
🙌 1