forge-import-settings-editor

Per-asset import settings are overridden by creating .import.toml sidecar files that merge with global configurations using a three-layer schema. This ensures individual file overrides are loaded and reprocessed correctly within the pipeline.

Yes, a schema-driven browser-based UI editor renders type-specific controls for each import setting. You can adjust configurations directly in the web interface and save to write the .import.toml sidecar file.

The three-layer settings merge combines defaults, global configurations, and per-asset overrides to tailor processing per file. This hierarchical merge ensures individual assets receive specific processing instructions while maintaining baseline settings.

Single-asset re-processing is supported directly from the web UI editor after modifying its import settings. The schema-driven editor applies the updated .import.toml sidecar to reprocess the specific asset independently.

No, the UI editor automatically handles TOML sidecar I/O for per-asset overrides. You adjust settings through the browser-based form, and the system writes the .import.toml file with minimal tooling required.

Per-asset import overrides are ideal when specific files require unique processing settings that differ from the global pipeline configuration. They allow granular control over individual assets without affecting the broader pipeline behavior.