-
Notifications
You must be signed in to change notification settings - Fork 9
Docs RFC: use <code>
for default values, sample values, and choice values?
#143
Comments
Looks good to me :-) For the (pedantic) record:
That is not entirely correct: the "regular" text comes with typographic quotes, cumbersome for copying/pasting. There's too many of them: https://en.wikipedia.org/wiki/Quotation_mark |
Any chance we can take the opportunity and to something about: https://ansible.fontein.de/collections/community/crypto/acme_account_info_module.html#return-account/public_account_key
Given that we do not put quotes around lists in that output, why do we do that with dicts? |
@russoz because the return type here is a string and not a dictionary. (https://github.com/ansible-collections/community.crypto/blob/main/plugins/modules/acme_account_info.py#L122) |
Should it be a string? |
It's a public key, so I would say yes. But that's totally off-topic to this discussion. :) |
Well you already know what I think ;) |
Thanks everyone! I'm going to merge that PR now, since nobody objected to the style either here, in the antsibull-docs repo, or in the docs or community meetings. |
Looks much better when using |
Summary
Right now, while values in the description that are (correctly) formtated with
C(...)
have code / teletype formatting, other auto-generated values such as choice list entries, defaults, and samples, are formatted as regular text (only with different colors). We want to change that.See ansible-community/antsibull-docs#38 (comment) - implementation is in ansible-community/antsibull-docs#42.
You can see some live examples here:
Compare these to the corresponding parts from the devel docs:
What are your opinions on this change? If nobody complains until after this week's community meeting (Wednesday 18:00-19:00 UTC), this change will get merged (and should eventually end up in the devel docs).
The text was updated successfully, but these errors were encountered: