Thinking about adding a flag to preserve clue HTML when provided (as discussed in #89) has resurfaced some inconsistency in the names of settings when they're provided from the command line vs. from the settings file vs. as a keyword in a Python environment. Ideally those would be exactly the same, and the cascading hierarchy of their application should be clear!
One technical note on that from the example at hand: if the command line flag is something like --preserve-html, the keyword argument in Python will use an underscore instead preserve_html) and the settings file keys should follow one or the other consistently.
Thinking about adding a flag to preserve clue HTML when provided (as discussed in #89) has resurfaced some inconsistency in the names of settings when they're provided from the command line vs. from the settings file vs. as a keyword in a Python environment. Ideally those would be exactly the same, and the cascading hierarchy of their application should be clear!
One technical note on that from the example at hand: if the command line flag is something like
--preserve-html, the keyword argument in Python will use an underscore insteadpreserve_html) and the settings file keys should follow one or the other consistently.