I have a search template of

$Before$.$MethodCall$($Parameter$)

, problem is..it matches on

<http://log.info|log.info> { }

as well as

<http://log.info|log.info> ()

, how can i get it to not match on lambda? I set complete match but it still doesn't listen to me, i want it to take the parentheses as is

remember that's it is a structural search, and therefore it searches based on structure of the syntax tree. Eg, from AST view,

<http://log.info|log.info> { }

is same as

<http://log.info|log.info>({ })

- and

{ }

gets matched to your

$Parameter$

@Roukanken so, that's the part that confuses me..if you look at the builtin kotlin ones, you get

{ $Parameter$ }

, this matches

<http://log.info|log.info> {}

only

remember that

func { }

is just a syntax sugar for

func( { } )

they have the exact same meaning which means ASTs look something like this: •

func { }

AST is: ◦ call a method (taken from whatever is

func

) and give it as parameters: ▪︎ lambda function •

func({ })

AST is same ↑ •

func { $parameter$ }

is: ◦ call a method (taken from whatever is

func

) and give it as parameters: ▪︎ lambda function • of which content is "return `$parameter$`"

yeah i get that part, but i'm saying that it is matching on

{}

which matches

log.debug {}

, and not

log.debug()

. so it definitely treats it differently

okay, I took out the big guns, and surprisingly there is a difference between 1st and 2nd This should be the tree JB is operating on

hm interesting. thank you. shall i raise a youtrack issue?

I'm reasonably sure this is an intended behaviour (as it would make more sense) but yeah, this basically stops you from matching what you want also fun is that

<http://log.info|log.info> { $x$ }

matches only the first one but

<http://log.info|log.info>({ $x$ })

matches both

haha right?

It's a plugin (PSI viewer I think?) mostly meant for coding plugins to manipulate code. It shows internal tree of code

okay, cool

(and theme is Palenight, from Material UI)