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
We have a case where we have some really long parameter names, which in the default formatting wraps all the descriptions into a single column. We work around this by specifying 120 columns, but a better solution would be if the formatter recognized that the names were over some threshold and then placed the description on the next line. So instead of the following:
required arguments:
--messaging-internal-format-uri MESSAGING_INTERNAL_FORMAT_URI Uri to publish messages in the
internal format. e.g.
rabbit://user:pass@localhost:5672
?exchange=some-name
--messaging-internal-format-with-raw-uri MESSAGING_INTERNAL_FORMAT_WITH_RAW_URI Uri to publish messages in the
internal format plus the raw
message. e.g.
rabbit://user:pass@localhost:5672
?exchange=some-other-name
It could look like the following:
required arguments:
--messaging-internal-format-uri MESSAGING_INTERNAL_FORMAT_URI
Uri to publish messages in the internal format. e.g.
rabbit://user:pass@localhost:5672?exchange=some-name
--messaging-internal-format-with-raw-uri MESSAGING_INTERNAL_FORMAT_WITH_RAW_URI
Uri to publish messages in the internal format plus the raw message. e.g.
rabbit://user:pass@localhost:5672?exchange=some-other-name
The text was updated successfully, but these errors were encountered:
We have a case where we have some really long parameter names, which in the default formatting wraps all the descriptions into a single column. We work around this by specifying 120 columns, but a better solution would be if the formatter recognized that the names were over some threshold and then placed the description on the next line. So instead of the following:
It could look like the following:
The text was updated successfully, but these errors were encountered: