fix: add shell language specifier to fn doc Flags code block #4377
+1
−1
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
aabhinavvvvvvv
requested review from
efiacor,
kispaljr,
liamfallon and
mozesl-nokia
as code owners
✅ Deploy Preview for kptdocs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Signed-off-by: aabhinavvvvvvv <abhinavguptaxia9213@gmail.com>
aabhinavvvvvvv
force-pushed
the
fix/fn-doc-flags-rendering
branch
from
71a0ddd to
cbc00e9
Compare
efiacor
approved these changes
Feb 9, 2026
liamfallon
approved these changes
Feb 10, 2026
CsatariGergely
approved these changes
Feb 10, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Docs: Fix Flags section rendering on fn doc page
Description
The "Flags" section on the
kpt fn docreference page does not render correctly. The fenced code block for the Flags section was missing theshelllanguage specifier, causing Hugo to interpret it as LaTeX math notation ($$...$$) instead of rendering it as a formatted code block.Fixes #4372
Motivation
All other fenced code blocks in the fn docs (including the Environment Variables section on the same page, and the Flags sections in
fn eval,fn render,fn source) use```shell. Thefn docFlags block was the only one using bare```, causing broken rendering on the documentation site.The fix adds the
shelllanguage specifier to match the convention used everywhere else.