docs: fix documentation links #1361
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Self links were not fully implemented, so I added them. Not all kubernetes-api references had links, adjusted the code to dynamically generate them. Also some naming inconsistencies in filenames were fixed so they are now the snakecase equivalent of the camelcase structs inside them. Otherwise generating the doc links would be quite difficult. Signed-off-by: Zoltán Reegn <zoltan.reegn@gmail.com>
wenchajun
approved these changes
Sep 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Self links were not fully implemented, so I added them.
Not all kubernetes-api references had links, adjusted the code to
dynamically generate them.
Also some naming inconsistencies in filenames were fixed so they are now
the snakecase equivalent of the camelcase structs inside them.
Otherwise generating the doc links would be quite difficult.
Signed-off-by: Zoltán Reegn zoltan.reegn@gmail.com
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: