PR #28 introduced the option g:lsp_async_completion, which allows to run lsp#omni#complete in sync-mode, ie. have the function wait for the results and return them, instead of returning v:none and adding the results later.
This allowed the omnifunc-implementation to be used in chaining completion-managers such as mucomplete, which rely on the (existence of) results to decide if the next completion should be called.
PR #391 changed this, returning v:none in either case, and thus breaking plugins which rely on the omnifunc actually returning any results.
PR #28 introduced the option
g:lsp_async_completion, which allows to runlsp#omni#completein sync-mode, ie. have the function wait for the results and return them, instead of returningv:noneand adding the results later.This allowed the omnifunc-implementation to be used in chaining completion-managers such as mucomplete, which rely on the (existence of) results to decide if the next completion should be called.
PR #391 changed this, returning
v:nonein either case, and thus breaking plugins which rely on the omnifunc actually returning any results.