Understanding Subscription Manager Custom Elements

Subscription Manager has several custom elements that are key components used throughout the Subscription Manager to encapsulate interaction-heavy functionality. This guide goes through several of those elements and how they are used in the template files.

Requirements

This article is intended for developers on v25 templates. You should already have a thorough understanding of the fundamentals of HTML, CSS, and JavaScript.

How to Tell What Version You’re On

Before the September 2024 release of v25, all Subscription Manager installations were on version 0, displayed in the Theme Designer as version 0.X.X. You can check which version you’re on by going to Ordergroove > Subscription > Subscription Manager.

Custom Elements

Datepicker

The datepicker element facilitates a styled calendar pop-up that allows the user to select a date. You can find more information about customizing the datepicker in this guide.

The datepicker is triggered by a button, and the selected date is saved into a hidden input field for form submission. The footer includes Cancel and Save buttons to manage the datepicker’s state. The example below demonstrates how to use the <sm-datepicker> element within a form:

1
<form action="{{ 'some_action' | action }}">
2
  <sm-datepicker data-submit-on-save="true">
3
    <button data-datepicker-trigger>Show datepicker</button>
4
    {% include 'ui-elements/datepicker-popover' %}
5
    <div data-slot="footer">
6
      <button data-datepicker-cancel>Cancel</button>
7
      <button data-datepicker-save>Save</button>
8
    </div>
9
    <input type="hidden" data-datepicker-input name="some_form_field" value="{{ some_date }}" required>
10
  </sm-datepicker>
11
</form>

Dialog

The <sm-dialog> element does not add any additional HTML, but it does automatically add extra event listeners and handles closing the dialog.

The dialog header includes a close button, but you can also include a button yourself that calls SMDialog.close.

The following is a sample dialog element built with the sm-dialog component:

1
<sm-dialog id="og-test-dialog">
2
  <dialog>
3
    {% set dialog_header_text = 'Skip upcoming order' %}
4
    {% include 'dialog-header' %}
5
    <div class="og-dialog-body">
6
      <p>
7
        By skipping your upcoming order, the order will instead send on the next available date based on the frequency
8
        you selected.
9
      </p>
10
    </div>
11
    <div class="og-dialog-footer">
12
      <button @click="{{ 'SMDialog.close' | js }}">Cancel</button>
13
      <button>Send now</button>
14
    </div>
15
  </dialog>
16
</sm-dialog>

To trigger a dialog opening, use a button with data-click-target and an @click event:

1
<button data-click-target="og-sku-swap-dialog-{{ subscription.public_id }}" @click="{{ '(e) => SMDialog.open(e)' | js }}">Open dialog</button>

Toggle

This implements a “disclosure widget” to hide and reveal content. The button to reveal the content should have a data-toggle-trigger attribute and the content to be revealed should have a data-toggle-content attribute.

The element handles adding the appropriate ARIA attributes to the trigger and animating the content in and out. When the content is revealed, the sm-toggle element will have a data-open attribute.

The following example demonstrates the correct use of the sm-toggle component:

1
<sm-toggle>
2
  <div>
3
    <button data-toggle-trigger aria-label="Order details"></button>
4
  </div>
5
  <div data-toggle-content>
6
    <p>Content to hide/reveal</p>
7
  </div>
8
</sm-toggle>