Variable completion sometimes breaks

[anantoghosh]

I'm not 100% sure when it happens, I'm using it with defold and this breaks only on the 'self' variables.

function init(self)
    self.lucky = true
end

Now autocomplete starts suggesting self.l, self.lu ... etc (as in screenshot)

After restarting atom, the problem goes away for the already declared variables (here: direction, moving, speed) but still breaks for any new variables declared.

On Atom 1.14.3 x64
Windows 10 x64

PS: Very useful extension, thanks for making this

[dapetcu21]

Thanks for the report. Will look into it, but it might take a while, as I will probably only free up in early April.

[pablomayobre]

I cannot replicate this issue in Atom 1.17 beta 3, Windows 10 x64, autocomplete-lua 0.8.1

I typed the same thing you posted but those erroneous suggestions just weren't there. Is there something I'm missing?

[dapetcu21]

This happened to me a few times as well lately. Not still exactly sure how to reproduce, but the issue is definitely there.