Extensions

Spring for Dart keeps much of an application's wiring in annotations, strings and configuration files: which bean a constructor gets, which property ${shop.name} reads, what a SpEL expression means. A plain Dart editor sees none of that. The editor extensions do. They jump from an injection point to its beans, show property values on hover, check expressions while you type and complete configuration keys.

Next to the Spring support there are extensions for the rest of the daily work: running and debugging Flutter apps, sending HTTP requests to your server, and themes made for the code.

Editors

Editor Status
Zed Available: four extensions
VS Code Planned
Android Studio and IntelliJ IDEA Planned

Zed extensions

Extension Summary
Spring for Dart A second language server for Spring for Dart: navigation from injection points to beans and from placeholders to properties, hovers, checks of SpEL, pointcuts, queries and config keys, SpEL highlighting, completion from the Spring metadata, snippets, and the Properties language
Flutter Tools Dart and Flutter as in VS Code: run and debug on every platform, hot reload on save, hot restart, Flutter DevTools, build_runner watch in the background, and 144 snippets that add their imports
HTTP Client IntelliJ IDEA's HTTP Client for Zed: run requests from .http files with a gutter button, environments, response chaining, and requests generated from routes and HTTP calls in 50 frameworks, Spring for Dart included
Farum Azula Themes Two dark themes, an opaque and a transparent one, with one syntax palette

The extensions are not in Zed's extension registry yet. They install from their GitHub repositories with one script; see Installation.

Where to start

Source