FOLLOW-UP: Dedicate a separate config field for computed source parent (from PR #215) #217
Description
Context
This follow-up task was identified during the review of PR #215.
Source PR: #215
PR Title: feat: add computed source type for derived/aggregated data
Suggested by: @claude[bot]
Task Description
The From field on SourceConfig is shared between REST/GraphQL sources (where it means "API endpoint URL") and computed sources (where it means "parent source name"). This semantic collision means a misconfigured from: https://... on a computed source would fail with a confusing "parent source not found" error.
Consider adding a dedicated field like parent or derives_from for computed sources, and updating From comments in both internal/config/config.go and parser.go to reflect the dual usage if the field is kept.
This issue was automatically created by prmonitor from PR review comments.