In qute, allow spaces between method parameters and only validate the return type of the method invocation when iterating over a method invocation

[gbourant]

The following image is the file angelozerr.html. As you can see, based on the formatting it highlights that the code has some errors.

To remove the error highlight i did the following, i changed

ifElementHasError(errorFields, errorKeys)} with
ifElementHasError(errorFields,errorKeys) }, I removed the space after the comma and added a space before the last curly bracket.

getErrorMessages(errorFields,errorKeys)} with
getErrorMessages(errorFields, errorKeys)} (added a space after the command and added a space before the last curly bracket)

After you fix those two errors you get a new one as shown in the image. So i changed {errorMessage} to { errorMessage} (added a space after the first curly bracket)

Reproducer: https://github.com/gbourant/qute-bugs

[fbricon]

Need to check but it might be fixed by #965

[fbricon]

@angelozerr #965 does NOT fix this bug

[angelozerr]

@gbourant let me invesitigate your problem.

If you write { errorMessage} it should be not a valid Qute expression (but perhaps the Qute parser is supporting that now?)

[gbourant]

@gbourant let me invesitigate your problem.

If you write { errorMessage} it should be not a valid Qute expression (but perhaps the Qute parser is supporting that now?)

Correct, i tried { errorMessage} and it does not work.

@mkouba, shouldn't we get a compile time error for this?

[angelozerr]

See doc at https://quarkus.pro/guides/qute-reference.html#identifiers

[angelozerr]

@gbourant another question is the following expression (parameter with space)

getErrorMessages(errorFields, errorKeys)

is working?

I ask you that because in our Qute support, you should see the type if verythinh is working good:

If you add an extra space we consider that it is not valid and the type is not displayed:

and it is the reason whyyour {errorMessage} is highlighted as an error since the type cannot be resolved.

[angelozerr]

We have a bug with validationerror of iterable:

This validation must not be applied for parameter.

[gbourant]

@gbourant another question is the following expression (parameter with space)

getErrorMessages(errorFields, errorKeys)

is working?

Yes it's working.