Qute Debugging support.

[angelozerr]

Here a demo:

[geoand]

Very cool!

[angelozerr]

Very cool!

Thanks @geoand but it is not finished. I need to improve Qute debugger, IJ Quarkus, vscode-quarkus and this PR to support debugging inside Java file.

On quarkus-langchain4j side, your engine builder must return a TemplateLocation with the proper uri source (which contains the class name, the method name and the annotation which defines the template). It will require to bump langchain4j to 3.29 because TemplateLocation#getSource() is available since 3.29

If I understood, it can be a problem for you.

After that, with this URI, Qute debugger will delegate the get of start line from Java file where template is defined inside annotation to IJ (with IJ Quarkus) and JDT (with vscode-quarkus) because those Java components are able to retrieve this start line information (thanks to AST).

[geoand]

If I understood, it can be a problem for you.

The project must be built to target Quarkus 3.27 (the LTS), nothing newer. This is a hard, non-negotiable requirement.
We'll need to find a way to dynamically call the required code (which shouldn't be hard) if we want to have this Qute debugger integration.

[angelozerr]

If I understood, it can be a problem for you.

The project must be built to target Quarkus 3.27 (the LTS), nothing newer. This is a hard, non-negotiable requirement.
We'll need to find a way to dynamically call the required code (which shouldn't be hard) if we want to have this Qute debugger integration.

Ok so the solution that I see is to store the Java uri info as template id instead of using TemplateLocation#getSource.

[geoand]

I assume this depends on langchain4j/langchain4j#4180

[angelozerr]

I assume this depends on langchain4j/langchain4j#4180

Exactly!