QuteProcessor - more concise format to report incorrect expressions

[mkouba]

• resolves Improve errors reporting of QuteProcessor #25724

[ERROR] 	[error]: Build step io.quarkus.qute.deployment.QuteProcessor#processTemplateErrors threw an exception: io.quarkus.qute.TemplateException: Found incorrect expressions (2):
[ERROR] 	[1] ItemResource/items.html:13 - {item.prices}: Property/method [prices] not found on class [org.acme.qute.Item] nor handled by an extension method
[ERROR] 	[2] ItemResource/items.html:20 - {cdi:foo}: @Named bean not found for [foo]

[mkouba]

CC @angelozerr

[gastaldi]

Looks good to me

[mkouba]

Looks good to me

Ok, let's wait for Angelo's review then ;-)

[angelozerr]

[ERROR] [1] ItemResource/items.html:13 - {item.prices}: Property/method [prices] not found on class [org.acme.qute.Item] nor handled by an extension method

I cannot test but it looks good to me,because it seems now you have an error per line, and it should be easy to write a pattern to extract information about file name, line number.

However, the 2 limitations that I can see are:

• if Qute template file is not hosted in src/main/resources/templates it should not work.
• do ou think you could add the column number of the start of the expression?

[mkouba]

• if Qute template file is not hosted in src/main/resources/templates it should not work.

Hm, didn't try this. Do you really mean "it should not work"? Or "it does not work"? ;-)

do ou think you could add the column number of the start of the expression?

I could :D

[mkouba]

do ou think you could add the column number of the start of the expression?

I could :D

@angelozerr Fixed.

[angelozerr]

Hm, didn't try this. Do you really mean "it should not work"? Or "it does not work"? ;-)

Not tested, it's just a question that I had (corner use case)

I could :D

Great thanks!

[mkouba]

Hm, didn't try this. Do you really mean "it should not work"? Or "it does not work"? ;-)

Not tested, it's just a question that I had (corner use case)

So we only validate the templates discovered in application archives and extension runtime artifacts. In other words, it should work in a quarkus app.