You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the flag is added to the cli, a complete list of the values keys is dumped, no matter the documentation comments present in the values.yaml file, and it exits. No readme file is generated.
Expected Behavior
List only the undocumented keys of values.yaml file if there is any, ignoring the ones tagged with the @ignored keyword.
Encountered this myself today while trying to setup strict checks for chart documentation. After a bit of trawling through changes, I loaded it up locally in the debugger.
While stepping through, I discovered that this appears to be an issue relating to parsing of the values descriptions. Specifically, the parsing expects the "old" metadata format, where the leading part of the doc comment includes the field path. If omitting this (using the newer style), the parsing finds no match on the key, so skips adding it to the keyToDescriptions map (match[1] is "" due to their being no explicit key in the comment), and the strict documentation check isn't aware of it, so fails.
Is there an existing issue for this?
Current Behavior
When the flag is added to the cli, a complete list of the values keys is dumped, no matter the documentation comments present in the values.yaml file, and it exits. No readme file is generated.
Expected Behavior
List only the undocumented keys of values.yaml file if there is any, ignoring the ones tagged with the
@ignored
keyword.Steps to reproduce it
example-charts/best-values-example
rm README.md
docker run --rm --volume "$(pwd):/helm-docs" -u $(id -u) jnorwood/helm-docs:latest helm-docs -x -l trace
I've tried versions from 1.11.0 to latest in docker, and the latest macos binary installed with homebrew, always with same result.
Reference Chart
example-charts/best-values-example present in the helm-docs repository.
Reference Template
No response
Environment
Link to
helm-docs
LogsNo response
Further Information
No response
The text was updated successfully, but these errors were encountered: