Quarkus Tools for IntelliJ 1.11.0 released!

Now any Template attribute will show the option to generate a corresponding Qute template, or navigate to the existing template file.

All Qute files paired with a corresponding Java resource support a number of language client features, such as go to definition, hover, autocompletion, etc.. Each of these we will explore further in the article

The Qute language server has support for built-in and user-defined Java classes, including parameter completion and validation for their methods. Take advantage of this to easily avoid Java related mistakes.

Alongside support for Java completion and validation, the extension also supports type hovering for built-in and user-defined Java classes.

Qute templates use sections in its templating language to power any logic required when compiling and displaying the resulting document. To support this, the extension’s Qute support populates a completion list with all available Qute sections, along with any parameters they take and a small code snippet of their usage.

Java and Qute validation is included for Qute templates with Quarkus Tools for IntelliJ, including diagnostics.

Paired with corresponding Java methods, built-in Java classes also have built-in Qute value resolvers made available by the Qute templating engine that are evaluated and output, or resolve to, a value. Quarkus Tools for IntelliJ supports completion, hover and snippet generation for these built-in value resolvers.

Template extension methods are used to extend the set of accessible properties of data objects. Qute support in Quarkus Tools for IntelliJ has support for marked @TemplateExtension Java methods, which extend a given data model.

Support for Directly Injecting Beans into Qute Templates

A CDI bean annotated with @Named can be referenced in any template through cdi and/or inject namespaces. Quarkus Tools for IntelliJ provides completion and definition navigation support for Beans.

While we had support for configuration profiles through property prefixing (eg. %dev.name), we now also support profile-aware files. We’ve added support for this, and many other features part of the MicroProfile 2.0 release.

We’ve added basic validation support for @Bulkhead, @Timeout, @Asynchronous, and @Scheduled annotations.

When launching a Quarkus application, the code lens URL endpoints now supports @ApplicationPath and will take its value into account.

In this example, the @ApplicationPath is set to /api, and the code on the method declaration (below) takes that into account when generating the URL.

At the end of the day, everyone wants to spend less time trying to hunt down some obscure setting, and more time developing the logic.

If you’re using the @CacheResult annotation on a method in your Java sources, we automatically suggest the settings available to configure it from your configuration file. It’s also fairly reactive to changes so you’ll always know if something has gone wrong.

@ConfigMapping is now also supported with some basic validation as well as completion for the application properties.