Directives

In Jamrock you can do some progressive enhancement just by using html attributes.

Those will tell the framework how to behave and decorate as needed, either on the server or client-side.

Special attributes

You can use prefixed attributes to set individual properties on a given element like class or style, other will be render as data-* attributes to declare behavior for JavaScript.

on:

This attribute tells the framework how to hydrate a client-side component on the browser, available values are: idle, visible, media, savedata and interaction.

Other values like on:click are rendered as onclick and so.

Client-side components are pretty basic, we'll explore them later on the scripting section.

use:

This will attach client-side behavior to the rendered element.

Same as on: and bind: attributes this requires JavaScript on the client-side to work.

Using on: attributes will configure how these hooks are loaded and instantiated.

bind:

You can collect some state from inputs and other form elements with JavaScript this way.

<input type="number" name="current_value" bind:value />

The framework will create a request with all bound elements on the current page, it's like simulating the <form> behavior.

As you noticed this requires JavaScript on the client-side.

We'll explore all these nuances on its dedicated section later.

class:

Will set a single className based on its evaluated value, any falsy value will ignore it.

<hr class:blank="{$$props.is_blank}" />

style:

This way you can set particular styles on the given element.

<span style:border="{$$props.has_border ? '1px solid red' : ''}">...</span>

Any falsy or empty value will omit the style from the render, 0 is taken as valid and will render the style-prop.

---

Raw HTML

You can use the @html attribute to render arbitrary text as HTML.

<div @html="<h1>It works!</h1>">...</div>

It would yield: <div><h1>It works!<h1></div>

<template>

Render HTML without any other element around, e.g.

<template @html="<h1>It works!</h1>" />

It would yield: <h1>It works!<h1>

These methods have no sanitization and they'll render as is, it may break your webpage if malformed, etc. Use them only if you control how the HTML is written.

---

HTML Forms

When building the state for your application forms are the preferred way to do it.

For shaping the request you can use @put, @post, @patch or @delete to set its method; the framework will decorate the rendered <form> to include the required attributes and elements as needed.

These directives will keep the form working as is, with no JavaScript being required to make it work.

@async

Adding this directive to your forms will enable JavaScript to process and handle the request originated by them.

The framework will evaluate the response to choose between patching the DOM, redirecting or reloading the page, etc.

An advantage of asynchronous forms is keeping the form state between requests, however certain elements will reset for now (e.g. <input type="file" />).

@reset

This directive will reset the form after a successful request.

Any response with a non 2xx status code is treated as a failure and the form will not be resetted.

@confirm

The user will be prompted with a confirm() dialog to submit the form, this is the dumbest way to make it conditional.

More advanced behavior can be made with JavaScript on the client-side, that's what a progressive enhancement is.

We're about to dig into that, let's continue!