Status Update
Comments
ar...@google.com <ar...@google.com>
an...@google.com <an...@google.com> #8
bu...@google.com <bu...@google.com> #9
bu...@google.com <bu...@google.com>
an...@google.com <an...@google.com>
an...@google.com <an...@google.com>
an...@google.com <an...@google.com> #10
Filed
Bugjuggler: (
bu...@google.com <bu...@google.com> #11
bu...@google.com <bu...@google.com> #12
I should wait for
* github.Issue: Get "
* github.Issue: Get "
bu...@google.com <bu...@google.com> #14
bu...@google.com <bu...@google.com>
an...@google.com <an...@google.com>
an...@google.com <an...@google.com>
cs...@google.com <cs...@google.com> #16
Reposting my UX POV here:
I'm personally not convinced yet that we should turn it off by default - I imagine IntelliJ had reasonable rationale for having it turned on, and I would prefer to make this decision based on data (whether from metrics or UXR) before we decide what the default is. It's also easy to disable, so without definitive data that says it's a bad default, I'm inclined to not deviate.
tn...@google.com <tn...@google.com> #17
Chris, I did ask IJ for their rationale (
I don't think "it's easy to disable" is a good reason to make something a default. In the absence of data, I think we should be able to reason about it. Why is knowing who wrote a function useful? Isn't the why the interesting part? And I think there is an actual cost to having this default be true -- it's distracting. How do we weigh the distraction of users against the potential benefit of somebody thinking to themselves "I wonder who wrote this?" I suspect the latter population is very very small -- and again, all the code inlay will tell them is "who", not "why". I think in nearly all cases where you want to know who wrote something, you also want to see why, which means bringing up the code annotations bar. So then is having code inlay hints saving you any effort? And again, we need to not just count its usefulness, but also its cost. Many users may leave this on not because they need it but because they're not sure what it's for, or just because they tend to follow defaults. I don't know how to collect data on this, but it does seem like something we can reason about.
IntelliJ is a very good product, but they're not infallible when it comes to defaults. For example, in Studio's early days they defaulted to virtual caret placement -- so we would override that one and a few others. To me, this seems like another case where I think the default is problematic, unless there is a good reason that hasn't been explained yet.
an...@google.com <an...@google.com> #18
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Koala Feature Drop | 2024.1.2 Canary 8
- Android Gradle Plugin 8.6.0-alpha08
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
co...@protonmail.com <co...@protonmail.com> #19
FWIW. I hate it. I always disable. This is a welcome change. thanks!
ge...@gmail.com <ge...@gmail.com> #20
I am with you, Tor, on this one. I don't care about who did what as much as why. It also takes up valuable vertical space in the editor, space that could be used to show actual lines of code. Thanks for this change (and Studio in general)!
Description
IntelliJ has various Inlay Hints -- tips added to the source code editor in place. It's generally adding important meta information about the code to help understand it, for example putting in parameter names for arguments in Java.
However, there is one for code author. It uses the version control to show the name of the person who most recently touched a method.
This doesn't seem important to persistently, for every single method, show in the editor. Most of the time you don't need to know who wrote something in order to read it -- it's visually and mentally distracting. It's trivial in the IDE to look it up when you actually want to know.
I don't think this should be on by default. (I filed