{#
TODO: it makes absolutely no sense to me to have a 'component' for lists and yet have multiple templates - one per type of list HTML element.
Obviously if you have a component you can *easily* abstract which tag you'd use and just keep 1 template since 99% of a list, ordered or not is identical.
E.g. pseudo-code: `include 'list.twig with {listType: ordered, listItems: [array], modifiers: 'some space delineated strings '}`
Having list-type prefixed variables everywhere also makes no sense at all - only one variable is required to flag an 'ol' vs 'ul'. This should be refactored to be simpler and DRYer.

/**
 * Available variables:
 * - ol_base_class - the base classname
 * - ol_modifiers - array of modifiers to add to the base classname
 * - ol_blockname - blockname prepended to the base classname
 * TODO: How or where are the actual items they defined?
 * Why are there two variables that look like they should be arrays of list items???
 * This one, and the one that's actually used: ol_items.
 * - listItems - TBD
 */
#}
{% set ol_base_class = ol_base_class|default('mds-l-flex-col') %}

<ol class="{{ ol_base_class }} {{ ol_modifiers }}">
  {% block list_content %}
    {% for ol_item in ol_items %}
      {% include "@mds/lists/_list-item.twig" with {
        list_item_label: ol_item.label,
        list_item_content: ol_item.content,
        li_base_class: ol_item.li_base_class,
        li_base_class: ol_item.li_base_class,
        li_modifiers: ol_item.li_modifiers,
        li_blockname: ol_item.li_blockname,
      } %}
    {% endfor %}
  {% endblock %}
</ol>