You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.
Right now, hovering over any whitespace or comments in an attribute set shows the value of the entire set. This is great for small sets, but it might be unwanted for large ones (e.g. nixos modules).
I guess my question is: when is it appropriate to show the value of an expression when hovering?
The text was updated successfully, but these errors were encountered:
I think it'd be a bit harsh if we only show the attr-set when hovering on the closing/opening bracket in an expression like
{foobar=1;}
Would it make sense to show an even shorter summary when hovering over comments (or at least whitespace)? Because I can imagine that it's useful to see what "context" you're in when editing lines in a large attr-set, however I'm not much into UX, so I'm not sure :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, hovering over any whitespace or comments in an attribute set shows the value of the entire set. This is great for small sets, but it might be unwanted for large ones (e.g. nixos modules).
I guess my question is: when is it appropriate to show the value of an expression when hovering?
The text was updated successfully, but these errors were encountered: