rocketship_paragraphs-5.0.0-alpha8/templates/rs--field--paragraph--p-010-children.html.twig

{#
/**
 * @file
 * Theme override for a field.
 *
 * To override output, copy the "field.html.twig" from the templates directory
 * to your theme's directory and customize it, just like customizing other
 * Drupal templates such as page.html.twig or node.html.twig.
 *
 * Instead of overriding the theming for all fields, you can also just override
 * theming for a subset of fields using
 * @link themeable Theme hook suggestions. @endlink For example,
 * here are some theme hook suggestions that can be used for a field_foo field
 * on an article node type:
 * - field--node--field-foo--article.html.twig
 * - field--node--field-foo.html.twig
 * - field--node--article.html.twig
 * - field--field-foo.html.twig
 * - field--text-with-summary.html.twig
 * - field.html.twig
 *
 * Available variables:
 * - attributes: HTML attributes for the containing element.
 * - label_hidden: Whether to show the field label or not.
 * - title_attributes: HTML attributes for the title.
 * - label: The label for the field.
 * - multiple: TRUE if a field can contain multiple items.
 * - items: List of all the field items. Each item contains:
 *   - attributes: List of HTML attributes for each item.
 *   - content: The field item's content.
 * - entity_type: The entity type to which the field belongs.
 * - field_name: The name of the field.
 * - field_type: The type of the field.
 * - label_display: The display settings for the label.
 *
 *
 * @see template_preprocess_field()
 */
#}

{%
  set classes = [
  'field',
  field_name ? 'field--name-' ~ field_name|clean_class,
  field_type ? 'field--type-' ~ field_type|clean_class,
  label_display ? 'field--label-' ~ label_display,

  field_name ? 'name-' ~ field_name|clean_class,
  field_type ? 'type-' ~ field_type|clean_class,
  label_display ? 'label-' ~ label_display
]
%}

<div{{ attributes.addClass(classes) }}>

  {% block field_content %}

    {# just always render the wrapper, no matter if it's multiple or not, it's easier for theming #}
    {# not using UL because slick slider needs to nest spans into it and that will break semantic validation #}
    <div class="field__items">

      {%
        set itemClasses = [
        'field__item',
        field_name ? 'field__item--name-' ~ field_name|clean_class,
        field_type ? 'field__item--type-' ~ field_type|clean_class,
        label_display ? 'field__item--label-' ~ label_display
      ]
      %}

      {% for item in items %}
        <div{{ item.attributes.addClass(itemClasses) }}>
          {{ item.content }}
        </div>
      {% endfor %}
    </div>

  {% endblock %}

</div>