feat(resolver): optional merged properties from multiple matching sources
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 0
- Avg merge
- 6h 46m
- Merged PRs (30d)
- 5
Description
Problem
Notebook TODO requests merged metadata across all sources, not only first-hit source.
Proposal
Add optional mode for resolve:
- default: first-hit behavior (current)
- optional: merge properties from all matching sources
API sketch
resolve(query, { merge: true })
Merge output
- properties.source: primary source
- properties.sources: array of contributing sources
- merged fields with deterministic precedence
Acceptance criteria
- Backward-compatible default behavior.
- Merge mode tested on airport + navaid examples.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the resolve entry point and the notebook TODO describing merged metadata across sources. Run or inspect the existing airport and navaid examples, then define the merge-mode behavior against the stated acceptance criteria: preserve first-hit defaults, report primary and contributing sources, and verify deterministic precedence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100