configuration

Automate project configuration by merging a root config.json with default values and interactively prompting for missing fields. The system prioritizes config.json values and validates input against a schema before saving.

Merging config.json with defaults works by reading the root file, applying sensible defaults for missing fields, and prompting one question at a time for required values. It validates against config.schema.json and presents a summary before saving.

Yes, you can validate user input during interactive configuration by integrating with a config.schema.json file. The system checks prompted values and existing config.json entries against the schema to ensure reliable setup.

The best way to handle missing fields in a config.json file is using an iterative, one-question-at-a-time workflow. This approach applies sensible defaults first, then interactively prompts for required missing values to ensure accurate setup.

Yes, config.json takes priority over interactive prompts during project setup. The configuration process reads the root config.json first, applies defaults for missing fields, and only prompts for values that remain undefined.