AlpineJS
Alpine JS brings simple client-side reactivity when you need it and integrates beautifully with CBWIRE.
Many page interactions don't warrant a full server roundtrip, such as toggling a modal or a hidden element. In these instances, we recommend using AlpineJS.
Installation
<head>
<script src="//unpkg.com/alpinejs" defer></script>
<!-- The "defer" attribute is important to ensure Alpine waits for CBWIRE to load first. -->
</head>For more installation information, visit Alpine Docs.
Templates
Below is an example of using AlpineJS to toggle a list on the page.
<div>
<div x-data="{ open: false }">
<button @click="open = true">Show More...</button>
<ul x-show="open" @click.away="open = false">
<li><button wire:click="archive">Archive</button></li>
<li><button wire:click="delete">Delete</button></li>
</ul>
</div>
</div>Shared State
CBWIRE has a powerful entangle() method that allows you to "entangle" a CBWIRE and AlpineJS data property. With entanglement, both client-side and server-side properties are instantly synchronized, regardless of whether the value was changed in CFML or client-side using JavaScript.
You need CBWIRE v2.3.6 or greater to use entangle().
This provides data model binding both client-side and server-side.
Consider this simple Counter component:
We define an AlpineJS property named counter and then call the built-in CBWIRE method entangle(), passing it the name of the server-side data property we want to bind with.
Next, we are incrementing our Counter in two separate ways:
Incrementing the counter by calling the increment() action using CBWIRE
Incrementing the AlpineJS property counter in JavaScript, triggering an immediate update to the server and re-rendering of the component.
Updating CBWIRE server-side on every AlpineJS property change is optional. You can also delay the server-side updates until the next CBWIRE request that goes out by chaining a .defer modifier like so.
Last updated