2023-01-13 19:43:42 +00:00
|
|
|
<!doctype html>
|
2023-01-31 14:45:51 +00:00
|
|
|
<html lang="{{ currentLocale }}">
|
2023-01-13 19:43:42 +00:00
|
|
|
<head>
|
|
|
|
<meta charset="utf-8">
|
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
2023-01-31 12:07:17 +00:00
|
|
|
<title>{{ template "title" . }} — Numerus</title>
|
2023-01-17 21:28:47 +00:00
|
|
|
<link rel="stylesheet" type="text/css" media="screen" href="/static/numerus.css">
|
2023-04-29 14:20:13 +00:00
|
|
|
<script src="/static/htmx@1.9.2.min.js"></script>
|
Reimplement the multiselect as a custom element
What i really set off on was to refactor the multiselect’s x-data
context to a separate JavaScript file.
I did not see the need at first, thinking that it would not matter
because it was used only in a template and i was not duplicating the
code in my files. However, i then realized that having the context
in the template means the visitor has to download it each and every time
it accesses a form with a multiselect, even if nothing changed, and,
worse, it would download it multiple times if there were many
multiselect controls.
It makes more sense to put all that into a file that the browser would
only download and parse once, if the proper caching is set.
Once i realized that, it was a shame that AlpineJS has no way to do
the same for the HTML structure[0], for the exact same reasons: not
wanting to download many times the same extra <template> and other
markup required to build the control for JavaScript users. And then i
remembered that this is supposed to be custom element’s main selling
point.
At first i tried to create a shadow DOW to replace the <select> with
the same <div> and <ul> that i used with Alpine, but it turns out that
<select> is not one of the allowed elements that can have a shadow root
attached[0].
Therefore, i changed the custom element to extend the <div> for the
<select> and <label> instead—the same element that had the x-init
context—, but i would have to define or include all the styles inside
the shadow DOM, and bring the lang attribute, for it to look like it
did before. Out with the shadow DOM, and modify the <div>’s contents
instead.
At this point the code was so far removed from the declarative way that
AlpineJS promotes that i did not see much value on using it, except for
its reactivity. But, given that this is such a small component, at the
end decided to write it all in plain JavaScript.
It is more code, at least looking only at the code i had to write, but
i love how i only have to add an is="numerus-multiselect" attribute to
HTML for it to work.
[0]: https://github.com/alpinejs/alpine/discussions/1205
[1]: https://developer.mozilla.org/en-US/docs/Web/API/Element/attachShadow
2023-03-17 13:55:12 +00:00
|
|
|
<script type="module" src="/static/numerus.js"></script>
|
2023-03-25 00:56:26 +00:00
|
|
|
<script defer src="/static/alpinejs@3.12.0.min.js"></script>
|
2023-01-13 19:43:42 +00:00
|
|
|
</head>
|
|
|
|
<body>
|
2023-01-17 21:28:47 +00:00
|
|
|
<header>
|
|
|
|
<h1><img src="/static/numerus.svg" alt="Numerus" width="261" height="33"></h1>
|
2023-03-07 10:52:09 +00:00
|
|
|
<details id="profile-menu" class="menu">
|
2023-01-23 17:52:18 +00:00
|
|
|
<summary>
|
|
|
|
<i class="ri-eye-close-line ri-3x"></i>
|
|
|
|
</summary>
|
2023-03-20 12:09:52 +00:00
|
|
|
<ul role="menu" class="action-menu" data-hx-push-url="false" data-hx-swap="beforeend">
|
2023-01-22 21:30:15 +00:00
|
|
|
<li role="presentation">
|
2023-03-20 12:09:52 +00:00
|
|
|
<a role="menuitem" href="{{ companyURI "/profile" }}" data-hx-boost="true">
|
2023-01-23 17:52:18 +00:00
|
|
|
<i class="ri-account-circle-line"></i>
|
Add the company relation and read-only form to edit
I do not have more time to update the update to the company today, but i
believe this is already a good amount of work for a commit.
The company is going to be used for row level security, as users will
only have access to the data from companies they are granted access, by
virtue of being in the company_user relation.
I did not know how add a row level security policy to the company_user
because i needed the to select on the same relation and this is not
allowed, because it would create an infinite loop.
Had to add the vat, pg_libphonenumber, and uri extensions in order to
validate VAT identification numbers, phone numbers, and URIs,
repectively. These libraries are not in Debian, but i created packages
for them all in https://dev.tandem.ws/tandem.
2023-01-24 20:46:07 +00:00
|
|
|
{{( pgettext "Account" "menu" )}}
|
|
|
|
</a>
|
|
|
|
</li>
|
|
|
|
<li role="presentation">
|
2023-03-21 10:58:54 +00:00
|
|
|
<a role="menuitem" href="{{ companyURI "/tax-details" }}" data-hx-boost="true">
|
Add the company relation and read-only form to edit
I do not have more time to update the update to the company today, but i
believe this is already a good amount of work for a commit.
The company is going to be used for row level security, as users will
only have access to the data from companies they are granted access, by
virtue of being in the company_user relation.
I did not know how add a row level security policy to the company_user
because i needed the to select on the same relation and this is not
allowed, because it would create an infinite loop.
Had to add the vat, pg_libphonenumber, and uri extensions in order to
validate VAT identification numbers, phone numbers, and URIs,
repectively. These libraries are not in Debian, but i created packages
for them all in https://dev.tandem.ws/tandem.
2023-01-24 20:46:07 +00:00
|
|
|
<i class="ri-vip-diamond-line"></i>
|
|
|
|
{{( pgettext "Tax Details" "menu" )}}
|
2023-01-23 17:52:18 +00:00
|
|
|
</a>
|
2023-01-22 21:30:15 +00:00
|
|
|
</li>
|
|
|
|
<li role="presentation">
|
2023-01-23 17:52:18 +00:00
|
|
|
<form method="POST" action="/logout">
|
2023-02-02 10:39:34 +00:00
|
|
|
{{ csrfToken }}
|
2023-01-23 17:52:18 +00:00
|
|
|
<button type="submit" role="menuitem">
|
|
|
|
<i class="ri-logout-circle-line"></i>
|
|
|
|
{{( pgettext "Logout" "action" )}}
|
|
|
|
</button>
|
|
|
|
</form>
|
2023-01-22 21:30:15 +00:00
|
|
|
</li>
|
2023-01-17 21:28:47 +00:00
|
|
|
</ul>
|
2023-01-23 17:52:18 +00:00
|
|
|
</details>
|
2023-01-17 21:28:47 +00:00
|
|
|
</header>
|
2023-03-23 09:55:02 +00:00
|
|
|
<nav aria-label="{{( pgettext "Main" "title" )}}" data-hx-target="main" data-hx-boost="true">
|
2023-01-29 14:14:31 +00:00
|
|
|
<ul>
|
2023-01-31 12:29:56 +00:00
|
|
|
<li><a href="{{ companyURI "/" }}">{{( pgettext "Dashboard" "nav" )}}</a></li>
|
2023-02-11 21:16:48 +00:00
|
|
|
<li><a href="{{ companyURI "/invoices" }}">{{( pgettext "Invoices" "nav" )}}</a></li>
|
2023-02-04 10:32:39 +00:00
|
|
|
<li><a href="{{ companyURI "/products" }}">{{( pgettext "Products" "nav" )}}</a></li>
|
2023-02-01 09:14:26 +00:00
|
|
|
<li><a href="{{ companyURI "/contacts" }}">{{( pgettext "Contacts" "nav" )}}</a></li>
|
2023-01-29 14:14:31 +00:00
|
|
|
</ul>
|
|
|
|
</nav>
|
2023-01-17 21:28:47 +00:00
|
|
|
<main>
|
2023-03-20 12:09:52 +00:00
|
|
|
{{- template "breadcrumbs" . }}
|
2023-01-22 20:41:50 +00:00
|
|
|
{{- template "content" . }}
|
2023-01-17 21:28:47 +00:00
|
|
|
</main>
|
2023-01-13 19:43:42 +00:00
|
|
|
</body>
|
2023-03-25 00:56:26 +00:00
|
|
|
<div x-data="snackbar">
|
|
|
|
<div x-show="show"
|
|
|
|
@click="dismiss"
|
|
|
|
x-cloak
|
|
|
|
x-transition:enter="enter"
|
|
|
|
x-transition:enter-start="start"
|
|
|
|
x-transition:enter-end="end"
|
|
|
|
x-transition:leave="leave"
|
|
|
|
x-transition:leave-start="start"
|
|
|
|
x-transition:leave-end="end"
|
|
|
|
role="alert">
|
|
|
|
<p x-text="toast"></p>
|
|
|
|
</div>
|
|
|
|
</div>
|
2023-01-13 19:43:42 +00:00
|
|
|
</html>
|