Auto complete no longer shows local variables

[ConnorAU]

After todays update, defined local variables no longer show in the autocomplete.
I tried toggling that new context setting but it didn't help. Disabling the extension fixed it.

[SkaceKamen]

I'll look into it.

[Wyqer]

As I guess it's some kind of connected to this, I don't open a new issue on this.

Since the update the findIf function is marked as "wrong" again.
Also it doesn't recognize local variables which are declared via params in the findIf scope.
As an overview I've put together an image of the errors.

[SkaceKamen]

Oh, yea, I didn't know findIf existed, will add it in next update.

[Wyqer]

As far as I know findIf was fine until the update. But I can be wrong, of course.
Basically we've now many "possibly undefined variable" warnings in our code. It seems there is an issue with scopes concerning select etc.

Again a picture which shows this strange behaviour.

[SkaceKamen]

Yea, that's because the system for checking correct combinations of commands is now more aggressive and won't allow you to just put something that isn't defined in middle of expression.

For the false positives, I forgot to add support for lambda functions (eg functions used in select and such) ... I'll have to work on that, in the meanwhile you can just disable the context aware checking.

[Wyqer]

No critical problem at all, just wanted to report it. :)
I'm looking forward for the upcoming updates and really appreciate your work.

[SkaceKamen]

This issue is fixed in 0.9.1, issue with inline functions moved to #37