{{ row.title }}
{% endif %} {% if row.amount %}{{ row.amount }}
{% endif %}{{ row.subtitle }}
{% endif %} {% if row.badges %}-
{% for m in row.meta %}
- {{ m.label }}:
- {{ m.value }}
{% comment %} Responsive data-table wrapper — renders the table on md+ and a card-stack fallback on mobile so RIMS list views don't blow past the viewport. Caller passes the full rendered table_html and the same rows as a list of dicts {title, subtitle?, badges?, meta?, href?, amount?, amount_hint?, actions?} so the mobile stack stays in sync with table headers. For most list views the cleaner path is to use approval_queue.html, which already includes both layouts. responsive_table is for cases where the existing table markup is complex enough that re-shaping it into the approval_queue contract isn't worth it — drop the table HTML in unchanged and provide row dicts for the mobile fallback. Args: table_html : pre-rendered