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
dnst command help uses lowercase single words to document command line options, while dnsi uses SNAKE_CASE.
One of our older more mature Rust products, Routinator, also uses the lowercase single word option style.
We should decide if we want consistency and if so with what? With our own Rust tools? With our earlier non-Rust tools? With other tools in the ecosystem?
Switching to lowercase single word option style for dnsi would at least make dnsi, dnst and routinator consistent with each other, but I note that even our RPKI tooling is not consistent as rtrtr uses UPPERCASE single word option style while krill and krillcuse lowercase single word option style (with the exception of URI).
The text was updated successfully, but these errors were encountered:
Historical Unix seems to be single word in lowercase. Unbound has only one option with an argument and it is listed as a lowercase word. NSD has plenty of options with arguments. In some cases a hyphen is used as in 'server-count'.
dnst
command help uses lowercase single words to document command line options, whilednsi
usesSNAKE_CASE
.One of our older more mature Rust products, Routinator, also uses the lowercase single word option style.
We should decide if we want consistency and if so with what? With our own Rust tools? With our earlier non-Rust tools? With other tools in the ecosystem?
Switching to lowercase single word option style for
dnsi
would at least makednsi
,dnst
androutinator
consistent with each other, but I note that even our RPKI tooling is not consistent asrtrtr
uses UPPERCASE single word option style whilekrill
andkrillc
use lowercase single word option style (with the exception ofURI
).The text was updated successfully, but these errors were encountered: