Problem
The app currently uses hard-coded demo data, making it difficult for merchants and contributors to customize the storefront without code changes.
Proposed Change
Add a YAML loader that maps merchant metadata and products into the existing Python models. The app should accept a configuration file path and populate the catalog automatically.
Acceptance Criteria
- App can start from a provided YAML file via CLI flag or config path
- Validation errors point to the failing field with clear messages
- README includes a sample command showing how to load a custom catalog
- Existing hard-coded demo still works as a fallback
Related
See ROADMAP.md Phase 2 - Catalog and Merchant Config
Contributor Lane: Catalog & Config (Issue 1/2)
Difficulty: Medium
Related Phase: Phase 2 - Catalog and Merchant Config
Problem
The app currently uses hard-coded demo data, making it difficult for merchants and contributors to customize the storefront without code changes.
Proposed Change
Add a YAML loader that maps merchant metadata and products into the existing Python models. The app should accept a configuration file path and populate the catalog automatically.
Acceptance Criteria
Related
See ROADMAP.md Phase 2 - Catalog and Merchant Config
Contributor Lane: Catalog & Config (Issue 1/2)
Difficulty: Medium
Related Phase: Phase 2 - Catalog and Merchant Config