Configuration Loading

Configuration Loading

Vyasac uses a layered configuration system to allow global defaults to be overridden by local folder settings.

Loading Order (Precedence)

When compiling a file, the environment is built in this order (last one wins):

1. Workspace Root vyasac.toml: Global settings (e.g. Project Title, default structure).
2. Workspace Root context.vy: Global definitions (Entities, Templates, Custom Commands).
3. Local vyasac.toml: Folder-specific settings.
4. Local context.vy: Folder-specific definitions.
5. In-File Definitions: command-def or set commands at the top of the file.

Projection Profiles (RFC 013)

When the compiler is executed with a projection target (e.g. vyasa build --projection voice), an additional layer of scoped precedence is automatically injected:

1. Global context.vy: Loaded first.
2. Projection context.vy: Loaded second (e.g. view/voice/context.vy). This allows projection-specific definitions (like voice markup or html-specific commands) to cleanly override global definitions without polluting the main semantic namespace.
3. Projection Templates: The builder automatically switches the template directory to the projection’s path (e.g., view/voice/templates).

Logic: config.rs

The apply_definitions function maps configuration nodes to the VyasaEnvironment. It handles:

• command-def: Registers new commands (metadata, validation rules).
• alias-def: Creates shortcuts (e.g. p -> paragraph).
• set entities: Populates the Entity Registry.
• set settings: Updates compiler flags (e.g. whitespace="preserve").

Structural vs Metadata

• Flow Commands: If a command is defined with category="flow" (e.g. chapter), encountering it updates the Context Stack (e.g. chapter.id=1).
• URN Generation: If urn="true", the command gets a unique ID generated from the active context and scheme.