What’s New in IntelliJ IDEA 2024.1 EAP? Top Features for Spring, HTTP, and GitHub Actions
The IntelliJ IDEA 2024.1 EAP 5 release brings powerful enhancements for Spring and other Java frameworks, richer HTTP client capabilities, improved GitHub Actions support, and various productivity tweaks such as JSON schema handling and automatic header completion, all aimed at boosting backend developers' efficiency.
Enhanced Support for Spring, Quarkus and Other Frameworks
Search Everywhere now includes an Endpoints tab, allowing developers to locate implementations of Spring, Quarkus, Micronaut, and Ktor endpoints directly.
IntelliJ IDEA provides auto‑completion for all beans in the application context and automatically wires them, including constructor‑injected dependencies and fields annotated with Lombok's @RequiredArgsConstructor.
The Spring diagram view is improved: clicking the Spring icon jumps to the related code, and new icons (Components, Controllers, Repositories) enhance visualization. Bean visibility can be toggled, with hidden beans shown on demand.
HTTP Client Improvements
The HTTP Client now supports additional authentication methods such as PKCE authorization code and device grant flows, and it can generate code_challenge and code_verifier automatically for PKCE requests.
It also uses Netty as the low‑level network library, adding SSL, proxy, and HTTP/2 support, and its toolbar matches the new UI style for a more polished experience.
GitHub Actions Support Enhancements
Workflow context completion now covers github.*, env.*, steps.*, and inputs.* expressions.
In action.yml files, developers can specify custom icons and colors via the branding feature, making actions easier to identify in the Marketplace and CI pipelines.
Docker image and tag suggestions are provided in workflow files, simplifying container integration.
JavaScript file‑path completion automatically suggests paths, streamlining script configuration.
Other Updates
JSON schema handling has been optimized, resulting in up to a ten‑fold speed increase for schema validation and completion, especially in Azure Pipelines files.
HTTP header completion is now available in common scenarios, such as Spring WebClient and RestAssured tests, with automatic pop‑ups for expected values.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Programmer DD
A tinkering programmer and author of "Spring Cloud Microservices in Action"
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
