Skip to content
AggregaAggrega
Select language: English

Use Aggrega in Visual Studio Code

This section covers the Aggrega extension for Visual Studio Code: what it needs, how it gets the compiler, its welcome page and features, selecting a Release, what happens when the language server is not running, and its commands and settings.

Visual Studio Code with the Aggrega view open beside an Aggregate: the Commands panel names the project folder, the Aggrega workspace and the Release above its operation buttons, the Registries, Catalog and Plugins panels sit below it, and the status bar reports the language server running.

The pages of this section

Editing features

  • Diagnostics — YAML and schema validation surfaced inline as you edit, and for every open file each time a language server starts, checked against the selected Release.
  • Go to Definition — jump from extends, implements, provider, uses, recipe, aggregate, manifest references to their target entity files.
  • Find References / Implementations — list every reference to or implementation of an entity.
  • Hover — kind-aware summaries for catalog and release entities. With a Release selected, the entity a reference names is the one that Release resolves it to: it is looked up through the catalog directories the Release builds against first, then among the documents it reads. With none selected, it is looked up among the documents the Aggrega workspace holds and the ones the language server has validated first, then through the catalog directories your configuration names for the whole workspace, wherever they sit — so a standard-library Component shows its summary either way.
  • Completion — context-aware suggestions for entity kinds, API versions, schema keywords, primitives, label values, providers, paths, and intra-document component keys.