fix: sample-queries.txt uses incorrect root field name 'bundles' instead of 'olmbundles'
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- graphql
- Domain
- api
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.
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.
- Dominant language
- Go
- Stars
- 213
- Forks
- 85
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 36
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.
More from operator-framework/operator-controller
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
epic epic/v1-api lifecycle/stale v1.x
Difficulty 5/5 Over a week Newbie friendliness 30/100
operator-framework/operator-controller#2727 · 2 comments ·
-
operator-framework/operator-controller#2686 · 2 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
operator-framework/operator-controller#2680 · 2 comments · 1 reaction ·
All issues in operator-framework/operator-controller
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·