-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Autocomplete and Hinter #1873
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
Autocomplete and Hinter #1873
Conversation
🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. |
This comment has been minimized.
This comment has been minimized.
!!!!!!!!!!!! thank you for working on this! there's actually a google summer of code project focused on autocomplete for the web editor, so I'm going to let them take the charge in reviewing this and making sure the UI/UX is good/is web accessible/keyboard shortcuts are good/etc. |
Didn't know about the ongoing progress. If possible, I'm also happy to work with the corresponding developer(s) to push it to the shipping state. Please let me know! |
Thank you for continuing to update this PR! Sorry that progress has been slow. It turns out that there's not a GSoC project focusing on this issue, so I'm happy to review it. |
Create Release Environment |
Thanks! Please let me know anything that I need to put more work on! |
|
One UI feedback—I think that the font size of the text in the hinter should be the same size as whatever the text size is set to in a user's preferences. This may need to be done in JS rather than CSS. |
Overall this works so well and I can't wait to refine it and merge it in!! |
Hi @catarak, when were you thinking to merge this? |
So sorry for the delay in updating the PR! I don't think I'll have time to resolve the problems until early September as I'm running for some submission deadlines. I'll try to update as soon as possible for it to be ready to merge. |
No worries at all! I really appreciate the work you have done so far ✨ |
Apologies for this taking so long to merge in! I clearly reached a place of burnout and am in the process of finding new leadership (see #2010). That being said, I am doing a lot better, and am focusing my attention on updating packages, documentation, closing pull requests, and organizing issues, so I will merge this one within the next month. |
Yay! One month anniversary today! 🥹 |
Hi @peilingjiang! Thank you so much for your patience and understanding during our transitional period. I'm still learning the ropes for this position so merging in PRs and deployment might take some time, but I'd definitely love to continue the efforts that went into this feature. Timeline wise, I'm hoping to get a flow established over the following month and will be delving into the PRs (including this one) within that time. 🙂 |
Hey @raclim any plan on merging this? Thanks! |
Hi @peilingjiang! I'm really sorry for not getting to this 😅 I'm currently away until the end of the week so I won't be as active here until then, but I'd still love to merge your work in! Would you be able to resolve some of the conflicts in this branch? |
@raclim I have resolved the conflicts, added the switch to turn it on and off, added tests for the switch, and updated the UI a little. It should be all ready to merge now. ![]() |
Let's do it! I'm waiting for this to be merged to start teaching P5.js using the native editor! 🥳🥳🥳 |
@raclim Please let me know if there's anything that needs an update! Thanks for the review! |
@peilingjiang Thanks so much for continuing to work on this! I just got back so I'll start looking over this today, and will hopefully get back to you on this by tomorrow! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Overall, I feel like this looks really great so far! :)
As noted in my other comments, I had some difficulty activating the feature without the noted line change within the show-hint.js
file. Visually, it also appeared a bit differently for me.

Please let me know if there was something I might've missed or done incorrectly while reviewing this, or go ahead with adding any updates, thanks!
Some of the requested changes have become outdated!
I looked through it with the updates and think it looks great! I also created a release environment for it. Thanks again so much for your hard work and super excited to see it live soon! :) |
Yay! 🥳🥳🥳 @peilingjiang, is there a way to trigger a command syntax suggestion? |
Resolves #99
I was looking for WIPs and issues regarding autocompletion and found #99. Although the issue has been idle for a while, I think this feature can greatly help beginners to start and help reduce typos and increase efficiency in general. It turns out that CodeMirror provides a great base for implementing it so I tried to use its hinter addon and build this PR.
In addition to autocompletion, the hinters also have links to the corresponding documentation page. Not exactly the same as requested in #99 but provides a similar reference capability.
Some more details of this implementation:
Ctrl-Space
.css
andjavascript
modes, as CodeMirror's HTML hinter works weirdly.circle
even when you typecic
as a start.I have verified that this pull request:
npm run lint
)develop
branch. (If I was asked to make more changes, I have made sure to rebase ontodevelop
then too)Fixes #123