You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that chained expressions do not work with the autocompleter. I was curious if there was any thought on how to support that?
For example, assuming a() returns an object, I would want a().<TAB> to show me that object's properties, but currently the autocompleter shows me globals instead. Looking at the code, I think it would work if lastExpressionRegex changed to select the entire expression. That would result in invoking the function multiple times, but that could be ok..
Yes, that's true, but I think in most cases the type returned is stable, especially without changing the arguments to the function. At any rate, it would do the right thing much more often than the current behavior, which never does the right thing in that scenario?
I noticed that chained expressions do not work with the autocompleter. I was curious if there was any thought on how to support that?
For example, assuming
a()
returns an object, I would wanta().<TAB>
to show me that object's properties, but currently the autocompleter shows me globals instead. Looking at the code, I think it would work iflastExpressionRegex
changed to select the entire expression. That would result in invoking the function multiple times, but that could be ok..cc @deoxxa
The text was updated successfully, but these errors were encountered: