[v0.9.9] TypeAhead || Configurable AutoComplete Plugin

Resources Community Resources
, ,
#3

Glad to hear you liked the plugin! Feel free to share any ideas/issues

1 Like
#4

v0.9.5 is out now!

This version focuses on improving how you share autocomplete suggestions with your developer team — making it more accessible and less time consuming.

Features

  • You can now export and import your autocomplete suggestions using a .luau file

  • Added multi-selection, allowing you to select multiple suggestions at once (more functionality coming in future updates)

  • Added a “Copy” option to the autocomplete suggestion frame

Hope you enjoy this update! Any feedback is appreciated.

1 Like
#5

v0.9.6 is out now!

This version focuses on improving how you interact with suggestions using multi-selection.

Features

  • You can now right click an autocomplete suggestion to open its context menu (Context menu actions will apply to all selected suggestions)

  • Fixed an issue where suggestion IDs were being converted from strings to numbers when importing from a file

Hope you enjoy this update! Any feedback is appreciated

1 Like
#6

woah this is really cool, I hope this gets popular

thank you my king :heart:

2 Likes
#7

v0.9.7 is out now!

Just a quick bug fix.

Features

  • Fixed an issue with cloning suggestions
1 Like
#8

Works great but the edit button seems to lead back to the create screen so I have to delete and recreate the trigger

1 Like
#9

nevermind I’m an idiot, what it should do instead is automatically fill in the fields with what you already have saved

1 Like
#10

v0.9.8 is out now!

QoL improvements.

Features

  • Fixed an issue where the edit button would autofill fields with wrong autocomplete suggestion data (Thanks to @D7L14 for pointing it out!)

  • Added icons to context menu buttons to make options easier to recognize

Hope you find these changes helpful!

1 Like
#11

v0.9.9 is out now!

This version focuses on improving how you can customize autocomplete suggestions.

Features

  • Added an option to change the icon of an autocomplete suggestion (The icon list is based on the CompletionItemKind enum)

  • Added an option to set the context in which autocomplete suggestion will appear

  • Updated the tutorial to include the newly added options

Hope you enjoy this update! Any feedback is appreciated.

1 Like
#12

Nice to see that there’s been an influx of ScriptEditorService plugins now. I used to have one way before ScriptEditorService was introduced.

Couldn’t you just call it “description” then?

Why the ?

Yeah, this really needs to be improved. Not just UI, but the UX just feels horrible just from thinking about the workflow. I recommend you use another UI library, such as:

Or I don’t know, try some frameworks like react-lua or Fusion. Or maybe just do native regular GUI

Compared to SimpleComplete (another autocomplete plugin), which has more features. What does this plugin offer in the long run?

1 Like
#13

Hello, thanks for the feedback!

Coincidentally, your plugin inspired me to create this plugin, so thanks for the idea! (btw you’ve made a blank hyperlink)

Oops, the period was meant to be there

Detail is the term used in the ScriptEditorService, so I didn’t bother changing it, but I can change it for readability tho

Thanks for the resources! I was unable to find any libraries at the time besides StudioWidgets (I mainly chose it so I wouldn’t have to create a Studio like UI from scratch.)

This plugin is a personal project created to gain some experience in plugin making. I’ve decided to share my work with others simply for the sake of it

1 Like
#14

:ok_hand:, maintaining a resource is quite hard when you’ve got stuff cramping in, so I would say commit to a resource instead of doing multiple resources (blatant mistake I did)

oh I accidentally made a double parentheses

Yeah, keeping it consistent could avoid mishaps in your code. But you should view your code into 2 sections, the logic section, and the UI section. The logic is where you use detail as the term, but in the UI you should use the more understood term, description.

True, we all hate doing UI from scratch

We all do :raised_hands: :+1:

1 Like
#15

I just looked at SimpleComplete and can say that my plugin’s purpose is a bit different from SimpleComplete’s (as far as I understood from the SimpleComplete post; if I’m wrong, feel free to correct me)

My plugin lets you create your own autocomplete suggestions, and that’s the only functionality it currently offers. You can use it to make fully custom autocomplete suggestions (e.g., you can create an autocomplete suggestion for return "Hello World" inside of functions), whereas SimpleComplete handles all the good stuff for you (again, as far as I understand from the SimpleComplete post)

1 Like
#16

Currently the closest thing to how TypeAhead works is snippets which allows you to define a module which returns a table of snippets which will be autocompleted, I agree the way both plugin works is very different and theres no value in comparing the two :V

1 Like
#18

After some consideration, I’ve decided to scrap the migration to a new UI library because I’m convinced the new plugin’s UI would look worse than it does with StudioWidgets. Why am I so sure? I suck at UI design lol (That’s actually the main reason I chose StudioWidgets in the first place)

1 Like
#19

The plugin’s UI/UX will be refactored with a new design that’s actually easier to work with, so stay tuned!

#20

Currently making some good progress.

image
image524×531 38.9 KB

1 Like
#21

Yeah, dang… UI/UX is definitely not your forte, you may need to reiterate on the design a couple more times, alternatively, get someone to do it for you :sweat_smile:

1 Like
#22

yeah im thinking about keeping StudioWidgets because none of the ui libraries works for me

#23

I could try using different colors and styles, since I’ve made a config file for all the UI settings. But I won’t, because roact is too hard to implement with my existing system.