New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cfg): write also enum choices when generating config.py files #381
Conversation
I would like to add one commit more that appends the "Default=" line to the comments above each config-parameter, and totally replicate the help-message. Currently the default-value is printed in the Should I do that? |
sure, that seems ok. |
With latest 2 commits now default-value are also printed on comments, and this PR is finished on my part. An additional change(169e849) is that the enum-choices are printed before the default-value. |
My apologies, just seen that there is a minor glitch in the generated configuration file (described in the review). |
+ Had to add an optional `as_rst=false` kwd in all`XxxEnum.info()` methods. + Added TCs for `info().
+ Had to add `as_rst=false` kwd to all `XxxEnum.info()` methods. + Added TCs for `info()`.
+ Had to add `as_rst=false` kwd to all `XxxEnum.info()` methods. + Added TCs for `info()`.
+ Had to add `as_rst=false` kwd to all `XxxEnum.info()` methods. + Added TCs for `info()`.
+ Had to add `as_rst=false` kwd to all `XxxEnum.info()` methods. + Added TCs for `info()`.
+ Had to add `as_rst=false` kwd to all `XxxEnum.info()` methods. + Added TCs for `info()`.
fix(help): finish #381 for RsT to print enum-choices
When generating the
config.py
file, explain the available enum-choices in the comment-lines, like help-message does.