Skip to content
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

code completion UI could be improved #1041

Closed
devoncarew opened this issue Apr 24, 2019 · 3 comments
Closed

code completion UI could be improved #1041

devoncarew opened this issue Apr 24, 2019 · 3 comments
Labels
closed-duplicate Closed in favor of an existing report P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug type-ux A user experience or user interface related issue
Milestone

Comments

@devoncarew
Copy link
Member

We should consider improving the UI for code completion. We're currently using the stock completion UI from codemirror; it expects results for what to show in terms of strings (a display string and a string to insert). The codemirror API also allows us to return arbitrary divs, so we would be able to extend it to better match the expressiveness of the IntelliJ or VS Code completion UIs.

@devoncarew devoncarew added type-enhancement A request for a change that isn't a bug P2 A bug or feature request we're likely to work on type-ux A user experience or user interface related issue labels Apr 24, 2019
@devoncarew
Copy link
Member Author

This is more important for the flutter_web examples, as the number of completion results is much larger than for simpler examples.

@devoncarew
Copy link
Member Author

Moving this forward to the flutter.dev project, but feel free to bump it further out.

@RedBrogdon RedBrogdon added this to the Backlog milestone Jul 24, 2019
johnpryan pushed a commit to johnpryan/dart-pad that referenced this issue Jun 27, 2023
@parlough
Copy link
Member

The code completion functionality has changed a bit since this issue was made, but has some remaining UX and DX concerns. Closing this issue in favor of addressing them together in #3010. Thanks for the discussion here!

@parlough parlough closed this as not planned Won't fix, can't repro, duplicate, stale Jun 17, 2024
@parlough parlough added the closed-duplicate Closed in favor of an existing report label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report P2 A bug or feature request we're likely to work on type-enhancement A request for a change that isn't a bug type-ux A user experience or user interface related issue
Projects
None yet
Development

No branches or pull requests

3 participants