Opening and closing table within a switch

Question

Within my matrix I have two blocks: Day and Event. Day is just a date field while the event block has two text fields.

What's the best way to wrap the event data, which needs to show up as a table format within this loop?

This currently spills everything out in the correct order but the table doesn't open and close correctly around the event block.

The final output should look something like

Title (h2)

Table open
TR
TR
TR
Table close

{% for block in entry.scheduleMatrix %}

{% switch block.type %}

{% case 'day' %}
            <h2>{{ block.day.format('l - F j, Y') }} </h2>
<table><tbody>

{% case 'event' %}
            <tr><td>{{ block.eventTime }}</td>
            <td>{{ block.eventName }}</td></tr>

{% endswitch %}
        </tbody>
</table>
{% endfor %}

Answer 1

I think the opening and closing tags in the table are in the wrong spot. Try opening and closing the table inside the event case.

{% for block in entry.scheduleMatrix %}

{% switch block.type %}

{% case 'day' %}
    <h2>{{ block.day.format('l - F j, Y') }} </h2>    
{% case 'event' %}
    <table>
        <tbody>
            <tr><td>{{ block.eventTime }}</td>
            <td>{{ block.eventName }}</td></tr>
        </tbody>
    </table>    
{% endswitch %}

{% endfor %}

Answer 2

An alternate solution would be to add a date field to each event block, you can then group blocks by date on output, and wouldn't have to worry about the client accidentally putting an event in the wrong order. Something like the following (although my syntax might be off a bit).

{% set blocksByDate = entry.scheduleMatrix|group(day|date("Y-m-d") ) %}
{% for day, blocks in blocksByDay %}
    {{ day.format('l - F j, Y') }}
    <table>
        <tbody>
            {% for block in blocks %}
                <tr>
                    <td>{{ block.eventTime }}</td>
                    <td>{{ block.eventName }}</td>
                </tr>
            {% endfor %}
        </tbody>
     </table>
{% endfor %}

Not tested.

Answer 3

Brandon sent over another post that answer this exact problem: Solution for Matrix-within-Matrix (or More Robust Table Fields)

{% for block in entry.myMatrixField %}

{# Find out if this is the first/last consecutive block of this type #}
{% set type = block.type.handle %}
{% set isFirstConsecutiveBlockOfType = (loop.first or type != block.getPrev().type.handle) %}
{% set isLastConsecutiveBlockOfType = (loop.last or type != block.getNext().type.handle) %}

{% switch type %}

    {% case 'stat' %}

        {% if isFirstConsecutiveBlockOfType %}
            <div class="stats">
        {% endif %}

        <!-- Stat block HTML -->

        {% if isLastConsecutiveBlockOfType %}
            </div>
        {% endif %}

    {% case 'quote' %}

        {% if isFirstConsecutiveBlockOfType %}
            <div class="quotes">
        {% endif %}

        <!-- Quote block HTML -->

        {% if isLastConsecutiveBlockOfType %}
            </div>
        {% endif %}

{% endswitch %}{% endfor %}