Seeing a regression to the eager 'val' completion with 737

It seems we are back to the immediate completion when 'val' is entered. I getting autocompletes to MapMatchers#value.

3 comments
Comment actions Permalink

I've noticed a bit more context. Seems only to happen in a scenario like:

I have

  esper.sendNow(...)

I want to capture the result of this expression in a val, so I start typing

  valesper.sendNow
      ^
      |  At this point I am offered the completion to MapMatcher#value

But since I want to declar a val I enter space, but that does the autocomplete.

Seems in this scenario my intention is ambiguous. And with the new 10.x autocomplete there may not
be much the plugin or idea can do to differentiate.

0
Comment actions Permalink

The plugin gets a chance to look at the 'completion char', ie ' ', and choose whether to autocomplete or not. I used this to avoid autocompleting in constructor parameters. http://youtrack.jetbrains.net/issue/SCL-2563

There may be some more cases where we could apply the same checks. But I'm not sure if this is one of them.

0
Comment actions Permalink

There may be some more cases where we could apply the same checks. But I'm not sure if this is one of them.


Agreed.

0

Please sign in to leave a comment.