Directive with options should not used include list of options with values such as True or False

[jaguarfi]

The questionnaires have some options that require the user to specify whether the value for some options is either True or False. However, If we really want to follow the syntax of reStructuredText and/or Sphinx, we must evaluate whether the options are added or not, and consequently convert the inclusion of those options to a True or False value.

The following example include the :show-model: and :reveal-model-at-max-submissions: options. Booth require a boolean value.

. questionnaire:: override-settings 40
  :title: Questionnaire with both options. (``:show-model:`` & ``:reveal-model-at-max-submissions:``)
  :submissions: 1
  :show-model: True
  :reveal-model-at-max-submissions: True
...

One example of the behaviour we should follow can be seen in the toctree directive. In the toctree directive If the user wants to hide the toctree, he/she only has to add the :hidden: option (True value), but if the user wants to see the toctree he/she do not need to add the option at all (False value)

.. toctree::
   :hidden:

   doc_1
   doc_2

We have some other directives in a-plus-rst-tools that have the same logic as the toctree, but for some reason the :show-model: and :reveal-model-at-max-submissions: options and some others have this weird behaviour.

[markkuriekkinen]

It was necessary to explicitly specify the True/False value so that the directive can override the default value set for the course. The default is either True or False depending on the course settings.

I don't remember this exactly, but there may also be a difference of defining the value or not defining it. If it is not defined, then it might not save the field in the config.yaml at all.

There was a reason for doing it this way, so it is not "just weird behaviour". Other implementations did not work correctly. The backwards-compatibility is also a major factor here.