Properties should be available recursively

[gbourant]

Assume you have 3 tags:

1. inputLabelText.html

      {#inputLabel /}
      {#inputText  /}

2. inputLabel.html

   <label {#if for??}for="{for}"{/if}>
       {title??}
   </label>

3. inputText.html

   <input {#if value??}value="{value}"{/if} />

So when the inputLabelText.html is used {#inputLabelText /} the properties of the other tags are not available for auto completion.

[angelozerr]

If I understansd you can write

{#inputLabelText title="foo" /}

Are you sure with that?

[gbourant]

Yeap, it seems that it doesn't work.

You can see the attached imaged but also i updated the project here.

Also, I do not know if this relevant to this project but the highlight breaks when the property value has a space.

[angelozerr]

I didnt' know that we could write this kind of user tag. That's very strange because if title has different type from different user tag you will have some error.

@mkouba is it an expected behavior?

Also, I do not know if this relevant to this project but the highlight breaks when the property value has a space.

I think it is a bug from our Qute parser, we need to fix it.

Those 2 issues comes from the Qute Language Server and are not linked to IJ himself (I mean that we will have the same problem for vscode and Eclipse IDE)

[angelozerr]

@gbourant I moved your issue in quarkus-ls github project since your 2 issues comes from Qute LS.

[mkouba]

@mkouba is it an expected behavior?

I'm not quite sure what behavior do you mean?

I don't think that args/parameters of a user tag should be validated at all because tags that are not executed in isolation can access data from the parent context.

Note that in Quarkus 3.5 there's a breaking change - a user tag is now executed as an isolated template by default (unlike in previous versions).