Reusable web components and infrastructure

You can retrieve the most recent cart content (in JSON) by importing the fetch cart. It will return a promise that is resolved when the cart is up-to-date. Because the theme implements a smart caching, you can call this several times without worrying about multiple Ajax calls being done:

<script type="module">
  import {fetchCart} from "theme";

  (async () => {
    const cartContent = await fetchCart(); // JSON cart content
  })();
</script>

When working with product media, it is often useful to be able to create new image tag based on a given media object. The theme gives you the necessary tools to do that with the createMediaImg which returns a new "img" element that can be added to the DOM. The first parameter is a valid media JavaScript object, the second an array of requested widths, and the last one an extra set of extra attributes to be added on the image tag. The theme takes care of all the hard work to generating all the correct URL.

<script type="module">
  import {createMediaImg} from "theme";

  const imageTag = createMediaImg(mediaObject, [60, 120], {"class": "thumbnail", "sizes": "60px"});
</script>

The theme also exposes a convenient imageLoaded that returns a promise that is resolved when the image is fully loaded:

<code><script type="module">
  import {imageLoaded} from "theme";

  (async () => {
    await imageLoaded(imgElement);
    // Here, the imgElement image is fully loaded
  })();
</script>

When listening to heavy events such as on scroll, it can be useful to throttle the callback so that it is not called too much time. You can use the theme built-in throttle or debounce methods to do that in an efficient way:

<script type="module">
  import {throttle, debounce} from "theme";

  window.addEventListener('scroll', throttle(() => {
    // Throttled function
  }));

  inputElement.addEventListener('keydown', debounce(() => {
   // This function will be debounced to be called once every 150ms
  }), 150);
</script>

Drawers are off-screen elements that allow to show extra information. The theme uses a shadow-DOM approach that allows to quickly create your own drawers. To open a drawer, you must create a "button" with an aria-controls referring to the actual drawer.

Basic usage

Here is the basic code:

{%- assign drawer_id = 'your-drawer-id' -%}

<button aria-controls="{{ drawer_id }}" aria-expanded="false">Open</button>

<x-drawer id="{{ drawer_id }}" class="drawer">
  <h2 slot="header">My drawer</h2>

  <p>Content</p>
</x-drawer>

As you can see, we are simply creating a button, and a custom elements. This component uses the shadow DOM to create itself (the template is defined in the assets/shadow-dom-templates.liquid file), so you do not have to add all the boilerplate code such as the close button. Everything is done automatically.

The drawer has two main slots:

• title: the title slot (it can be any element such as a simple h2 or a complex div) will be automatically positioned inside the header of the drawer.
• default: everything that has not a named slot is automatically placed into the drawer's body.

Events

Every dialogs (such as a drawer) emits the following events that you can listen to:

• dialog:after-show: this event is triggered once the drawer has completely opened (after the animation)
• dialog:after-hide: this event is triggered once the drawer has completely closed (after the animation)

Methods

Once you have retrieved a specific drawer instance, you can the show and hide methods. Those returns a promise being resolved once the drawer has completely opened or closed, respectively:

const drawer = document.querySelector('.your-drawer');
drawer.show(); // Open the drawer and return a promise
drawer.hide(); // Close the drawer and return a promise

Advanced usage

Sometimes, you may need to create your own custom drawer while still reusing the appearance and accessibility benefits of the default drawer.

Because our themes export all components, can create your own customized drawers and register them as your own custom elements:

<script type="module">
  import {Drawer} from "{{ 'theme.js' | asset_url }}"; // Import the theme web component

  // Extend it
  class CustomDrawer extends Drawer {

  }

  // Create the custom elements
  window.customElements.define('custom-drawer', CustomDrawer);
</script>

{%- assign popover_id = 'your-popover-id' -%}

<button aria-controls="{{ drawer_id }}" aria-expanded="false">Open</button>

<x-popover id="{{ popover_id }}" anchor-vertical="start" anchor-horizontal="center" class="popover">
  <h2 slot="title">My popover</h2>

  <p>Content</p>
</x-popover>

The anchor-vertical and anchor-horizontal supports the values "start", "center" or "end" and allow to control how the drawer is being opened relative to its closest positioned parent.

By default, on product page, quick buy... the theme adds the product in Ajax without leaving the page. You can actually very easily make your custom product form being the same by adding the is="product-form" attribute to any product form:

{%- form 'product', product, is: 'product-form' -%}
  Your code

  <button type="submit">Buy</button>
{%- endfor -%}

This form will automatically be "augmented" thanks to the is attribute. Once a customer click on the button, it will follow the theme behavior (such as adding the product in Ajax).