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 customizing the usage output with setSectionKeys or getSectionMap there is still a large part of the usage message created in Help.detailedSynopsis. One could either take the whole detailed synopsis as is or one would need to override the whole method.
Split Help.detailedSynopsis into meaningful methods. Enable the help sections (customized by setSectionKeys or getSectionMap) to customize the detailed synopsis in a finer grained manner.
Do not break the api (should be possible).
Suggested new help sections would be something like:
detailedOptions
detailedParameters
detailedCommandName
Probably not as simple as I initially thought because of how the texttable is built and because of abbreviatedSynopsis.
The text was updated successfully, but these errors were encountered:
SysLord
changed the title
Customize usage in detail by spliting Help.detailedSynopsis
Customize usage in detail by splitting Help.detailedSynopsis
Dec 17, 2018
Thanks for raising this.
Can you provide some more detail on what you are trying to achieve? Some examples describing your specific use case(s) would be helpful.
When customizing the usage output with setSectionKeys or getSectionMap there is still a large part of the usage message created in Help.detailedSynopsis. One could either take the whole detailed synopsis as is or one would need to override the whole method.
Split Help.detailedSynopsis into meaningful methods. Enable the help sections (customized by setSectionKeys or getSectionMap) to customize the detailed synopsis in a finer grained manner.
Do not break the api (should be possible).
Suggested new help sections would be something like:
Probably not as simple as I initially thought because of how the texttable is built and because of abbreviatedSynopsis.
The text was updated successfully, but these errors were encountered: