Usage

Properties & Attributes

Many components have properties that can be set using attributes. For example, buttons accept a size attribute that maps to the size property which dictates the button’s size.

<ahi-button size="small">Click me</ahi-button>

        
  
        
      

Some properties are boolean, so they only have true/false values. To activate a boolean property, add the corresponding attribute without a value.

<ahi-button disabled>Click me</ahi-button>

        
  
        
      

In rare cases, a property may require an array, an object, or a function. For example, to customize the user menu’s user, you set the user property to an object. This must be done with JavaScript.

<ahi-user-menu></ahi-user-menu>

<script>
  const menu = document.querySelector('ahi-user-menu');
  menu.user = {
    name: 'John Doe',
    email: 'john.doe@azaleahealth.com',
    initials: 'JD',
    title: 'Software Developer'
  };
</script>

        
  
        
      

Refer to a component’s documentation for a complete list of its properties.

Events

You can listen for standard events such as click, mouseover, etc. as you normally would. However, it’s important to note that many events emitted within a component’s shadow root will be retargeted to the host element. This may result in, for example, multiple click handlers executing even if the user clicks just once. Furthermore, event.target will point to the host element, making things even more confusing.

As a result, you should almost always listen for custom events instead. For example, instead of listening to click to determine when an <ahi-checkbox> gets toggled, listen to ahi-change.

<ahi-checkbox>Check me</ahi-checkbox>

<script>
  const checkbox = document.querySelector('ahi-checkbox');
  checkbox.addEventListener('ahi-change', event => {
    console.log(event.target.checked ? 'checked' : 'not checked');
  });
</script>

        
  
        
      

All custom events are prefixed with ahi- to prevent collisions with standard events and other libraries. Refer to a component’s documentation for a complete list of its custom events.

Methods

Some components have methods you can call to trigger various behaviors. For example, you can set focus on an input using the focus() method.

<ahi-input></ahi-input>

<script>
  const input = document.querySelector('ahi-input');
  input.focus();
</script>

        
  
        
      

Refer to a component’s documentation for a complete list of its methods and their arguments.

Slots

Many components use slots to accept content inside of them. The most common slot is the default slot, which includes any content inside the component that doesn’t have a slot attribute.

For example, a button’s default slot is used to populate its label.

<ahi-button>Click me</ahi-button>

        
  
        
      

Some components also have named slots. A named slot can be populated by adding a child element with the appropriate slot attribute. Notice how the icon below has the slot="prefix" attribute? This tells the component to place the icon into its prefix slot.

<ahi-button>
  <ahi-icon slot="prefix" name="cloud-download"></ahi-icon>
  Save
</ahi-button>

        
  
        
      

The location of a named slot doesn’t matter. You can put it anywhere inside the component and the browser will move it to the right place automatically!

Refer to a component’s documentation for a complete list of available slots.

Don’t use self-closing tags

Custom elements cannot have self-closing tags. Similar to <script> and <textarea>, you must always include the full closing tag.

<!-- Don't do this -->
<ahi-input />

<!-- Always do this -->
<ahi-input></ahi-input>

        
  
        
      

Differences from native elements

You might expect similarly named elements to share the same API as native HTML elements, but this is not always the case. Azalea Kit UI components are not designed to be one-to-one replacements for their HTML counterparts.

For example, <button> and <ahi-button> both have a type attribute, but the native one defaults to submit while the Azalea Kit UI one defaults to button since this is a better default for most users.

Waiting for components to load

Web components are registered with JavaScript, so depending on how and when you load them, you may notice a Flash of Undefined Custom Elements (FOUCE) when the page loads. There are a couple ways to prevent this, both of which are described in the linked article.

One option is to use the :defined CSS pseudo-class to “hide” custom elements that haven’t been registered yet. You can scope it to specific tags or you can hide all undefined custom elements as shown below.

:not(:defined) {
  visibility: hidden;
}

        
  
        
      

As soon as a custom element is registered, it will immediately appear with all of its styles, effectively eliminating FOUCE. Note the use of visibility: hidden instead of display: none to reduce shifting as elements are registered. The drawback to this approach is that custom elements can potentially appear one by one instead of all at the same time.

Another option is to use customElements.whenDefined() which returns a promise that resolves when the specified element gets registered. You’ll probably want to use it with Promise.allSettled() in case an element fails to load for some reason.

A clever way to use this method is to hide the <body> with opacity: 0 and add a class that fades it in as soon as all your custom elements are defined.

<style>
  body {
    opacity: 0;
  }

  body.ready {
    opacity: 1;
    transition: 0.25s opacity;
  }
</style>

<script type="module">
  await Promise.allSettled([
    customElements.whenDefined('ahi-button'),
    customElements.whenDefined('ahi-card'),
    customElements.whenDefined('ahi-menu')
  ]);

  // Button, card, and menu are registered now! Add
  // the `ready` class so the UI fades in.
  document.body.classList.add('ready');
</script>

        
  
        
      

Component rendering and updating

Azalea Kit UI components are built with Lit. To optimize performance and reduce re-renders, Lit batches component updates. This means changing multiple attributes or properties at the same time will result in just a single re-render. In most cases, this isn’t an issue, but there may be times you’ll need to wait for the component to update before continuing.

Consider this example. We’re going to change the checked property of the checkbox and observe its corresponding checked attribute, which happens to reflect.

const checkbox = document.querySelector('ahi-checkbox');
checkbox.checked = true;

console.log(checkbox.hasAttribute('checked')); // false

        
  
        
      

You would probably expect this to be true instead of false, but the component hasn’t had a chance to re-render yet so the attribute doesn’t exist when hasAttribute() is called. Since changes are batched, we need to wait for the update before proceeding. This can be done using the updateComplete property, which is available on all Lit-based components.

const checkbox = document.querySelector('ahi-checkbox');
checkbox.checked = true;

checkbox.updateComplete.then(() => {
  console.log(checkbox.hasAttribute('checked')); // true
});

        
  
        
      

This time we see an empty string, which means the boolean attribute is now present.

Avoid using setTimeout() or requestAnimationFrame() in situations like this. They might work, but it’s far more reliable to use updateComplete instead.

VSCode Completion

Azalea Kit UI ships with a file called vscode.html-custom-data.json that can be used to describe its components to Visual Studio Code. This enables code completion for components (also known as “code hinting” or “IntelliSense”). To enable it, you need to tell VS Code where the file is:

1. Install Azalea Kit UI
2. If it doesn’t already exist, create a folder called .vscode at the root of your project
3. If it doesn’t already exist, create a file inside that folder called settings.json
4. Add the following to the file:

{
  "html.customData": ["./node_modules/@azaleahealth/azalea-kit-ui/dist/vscode.html-custom-data.json"]
}

        
  
        
      

If settings.json already exists, simply add the above line to the root of the object. Note that you may need to restart VS Code for the changes to take affect.