allow changing some properties of keyword completions #17
Conversation
|
I think, rather than trying to make the package support all these options, it makes more sense to provide an option to disable keyword completion entirely, and have people who want something like this do that and use |
|
I think that would be a lot more work for us. Generally we prefer adding options if something already does very nearly what we want, instead of cloning an entirely new implementation into our own codebase. We've already forked for this fix, so if there's any way to get something like this upstream, I'm all ears. Otherwise, this is the easiest and most time-effective solution for us right now. |
LoganDark
force-pushed
the
keyword-complete-options
branch
from
28163bc to
efb1296
Compare
FEATURE: The new `keywordCompletion` option can be used to define what kind of completions are generated for keywords. Issue #17
|
Does attached patch, which allows you to pass in a function that builds up the keyword completions, work for you? |
|
@marijnh yeah! |
|
Great. I've tagged 6.8.0. |
right now the keyword completions are impossible to really change in any way, and it's super annoying, because we'd like to have autocomplete sections in our app, but if we put anything in any section, that section will placed below all the hundreds of keywords. we'd love to put the keywords in a section below the other far more important stuff