-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve UX when completing struct #190
Improve UX when completing struct #190
Conversation
This PR also includes another fix, which is that functions or macros with arity 0 should not appear in the autocomplete of pipelines.
…e-ux-when-completing-single-module
I gave you an example of where fuzzy search comes in handy. Providing a different example where you don't think it's handy doesn't make your case. I think it's important, and we already have it for other types of completions. I've looked at this, and it's pretty complicated for what you get. Let's not focus on documentation right now, as that's the lion's share of the complexity here. |
Fixes the first part of #182
This PR has two improvements:
The first one is related to 182 issues. Additionally, I don't think we need fuzzy search. For example, if the target is
%Document.Lines{}
, without fuzzy search, we can simply type%Doc
and then press enter or tab for auto-completion. More options will appear automatically and we can filter by typingl
. With fuzzy search, maybe we could complete it by typing %Docl, but you need to remember that this module exists in advance. I don't think this experience is good. The current way is already very convenient for me.The second improvement adds structure documentation, including fields, types and default values. I really like this UI but I'm unsure if you guys like the code implementation too. I'd like to hear your opinions first before adding more tests.CleanShot.2023-05-29.at.15.23.59.mp4