operator-framework / operator-framework/operator-controller
fix: sample-queries.txt uses incorrect root field name 'bundles' instead of 'olmbundles'
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 213
- Forks
- 85
- Avg merge
- 2d 1m
- Merged PRs (30d)
- 38
Description
Summary
The file internal/catalogd/graphql/sample-queries.txt contains several GraphQL query examples that reference the root field name bundles, but the dynamic schema generator derives the field name from the schema name (olm.bundle → olmbundles). As written, those sample queries will fail for users.
Affected lines (approx.)
- Line 82:
bundles(limit: 5) { - Line 121:
bundles(limit: 20) { - Line 145:
bundles(limit: 10) { - Line 163:
bundles(limit: 10) {
Suggested fix
Replace all occurrences of bundles( with olmbundles( in internal/catalogd/graphql/sample-queries.txt.
References
- Downstream PR that introduced this file: https://github.com/openshift/operator-framework-operator-controller/pull/738
- Review comment that surfaced this issue: https://github.com/openshift/operator-framework-operator-controller/pull/738#discussion_r3307700386
Reported by @grokspawn.
Contributor guide
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
Open internal/catalogd/graphql/sample-queries.txt and inspect the four affected query examples around lines 82, 121, 145, and 163. Compare their root field names with the stated olm.bundle schema naming, update the examples as needed, and verify that no incorrect bundles( references remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 90/100