Zo is het nu:

Beter zo:

• Toon 50 rows per pagina
• Toon i.p.v paginanummers: 1-50, 51-100, 101-150 etc.
• Maak toegankelijker met enkele aria-label's e.a. Zie voorbeeld hieronder.
• Er staan drie verborgen elementen in de code (<li class="afp-page" hidden=""><a href="#"></a></li>). Is dat normaal?

<nav aria-label="Pagination">
    <ul>
        <li class="afp-first">
            <a href="…" aria-label="First page">
                <al-ico type="arrow-left-double" aria-hidden="true"></al-ico>
            </a>
        </li>
        <li class="afp-page afp-active" data-page="1"><a href="…">1 - 50</a></li>
        <li class="afp-page" data-page="2"><a href="…"">51 - 100</a></li>
        <li class="afp-next">
                <a href="#" aria-label="Next Page">
                    <al-ico type="arrow-right" aria-hidden="true"></al-ico>
                </a>
                <!-- En ook doen voor previous page dus 🙂 -->
        </li>
        <li class="afp-last">
            <a href="…" aria-label="Last page">
                <al-ico type="arrow-right-double" aria-hidden="true"></al-ico>
            </a>
        </li>
    </ul>
</nav>

It should be possible to cache certain data on the client side.

Use cases

Selects

Relation selects (Belongs To, HABTM, ...) fetch data from the server. These individual items should be cached so they remain in the localStorage, for example.

Searching in the select should then also look through these cached items in case there is no internet connection.

Adding new data

Sometimes new data is added, but there is no internet connection. In that case, the new data should be cached locally and created as soon as a connection is available.

How?

Some kind of class should be created that is somehow analogous to the Model. A client-side Model instance, kind of.

It should be possible to search, create, update, ... records.

Should this be a part of alchemy itself, or alchemy-form?

Since it's really specific to the browser it should probably be in a plugin, alchemy-form seems reasonable.

Right now the filter inputs are simple text inputs, with no way of defining things like "gt" or "includes" etc.