-
Notifications
You must be signed in to change notification settings - Fork 15
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
In qute, allow spaces between method parameters and only validate the return type of the method invocation when iterating over a method invocation #966
Comments
Need to check but it might be fixed by #965 |
@angelozerr #965 does NOT fix this bug |
@gbourant let me invesitigate your problem. If you write |
@gbourant another question is the following expression (parameter with space)
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. |
Yes it's working. |
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
@angelozerr https://quarkus.io/guides/qute-reference#identifiers is the correct link 😉 quarkus.pro is 👎 |
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
Fixes redhat-developer#966 Signed-off-by: azerr <azerr@redhat.com>
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)}
withifElementHasError(errorFields,errorKeys) }
, I removed the space after the comma and added a space before the last curly bracket.getErrorMessages(errorFields,errorKeys)}
withgetErrorMessages(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
The text was updated successfully, but these errors were encountered: