Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trailing closure and use closure literals content assist prefs together produce strange selection #626

Closed
eric-milles opened this issue Jul 8, 2018 · 0 comments
Milestone

Comments

@eric-milles
Copy link
Member

Assuming "Place trailing closure arguments after closing parenthesis" is checked (current default) and other content assist preferences are default as well, and given:

contribute(currentType()) {
  method name: 'foo', params: [bar: String, block: Closure]
}
fo|

Content assist at | with "Use closure literals for closure arguments" checked gives foo(bar) { it } -- replace "{ it }" with "{ }" and selection/caret goes inside literal instead of covering it. This matched end state of #625.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant