[Feature Request]: Incorrect links to multi-version CRDs
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- documentation
Research direction
No source file or test is named in issue #60. Start by locating the generator logic that creates Markdown anchors and links for versioned CRD resource types, and compare its expected behavior with the linked Kubernetes Docs example. Done means v2 Foo and FooList links jump to their v2 headings rather than the v1 headings.
Written by the indexing model from the issue text.
Description
I used crd-ref-docs to generate API documentation for a multi-version CRD.
# API Reference
## Packages
- [example.dev/v1](#exampledevv1)
- [example.dev/v2](#exampledevv2)
## example.dev/v1
### Resource Types
- [Foo](#foo)
- [FooList](#foolist)
#### Foo
<- Jump to here
## example.dev/v2
### Resource Types
- [Foo](#foo) <- Click this
- [FooList](#foolist)
#### Foo
<- Expect to jump to here
Clicking on the v2 version of Foo redirects to the v1 version of Foo
Refer to the implementation of Kubernetes Docs
- Dominant language
- Go
- Stars
- 174
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 elastic/crd-ref-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
elastic/crd-ref-docs#204 ·
-
Support for +kubebuilder:validation:Required and omitemptyPossibly taken @swathinsankaran claimed this 111 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
elastic/crd-ref-docs#198 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
elastic/crd-ref-docs#191 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
elastic/crd-ref-docs#188 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
elastic/crd-ref-docs#182 ·
All issues in elastic/crd-ref-docs
Similar issues
-
bug go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
genkit-ai/genkit#6761 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
ready
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
kubeflow/pipelines#14784 · 1 comment ·
Maintainers usually reply within 2 days
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
trust: update-propagation-directive requires developer mode while add and remove do notPossibly taken @bhuvan-somisetty claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days