@optionfactory/fml 9.0.0-rc10 → 9.0.0-rc12

package/dist/web-types.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/web-types",
   "name": "@optionfactory/fml",
-  "version": "9.0.0-rc10",
+  "version": "9.0.0-rc12",
   "description-markup": "none",
   "contributions": {
     "html": {
@@ -405,11 +405,11 @@
         },
         {
           "name": "ful-input",
-          "description": "A labelled text input. Use type to pick any native input type, or textarea; keep names the characters that survive a keystroke and reject the ones that do not, the caret staying among the survivors, and the uppercase and trim claims shape the value before it is read; v-type=number decodes the value to a number, blank staying null and a value that does not decode kept as it is, an undeclared type defaulting to number. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
+          "description": "A labelled text input. Use type to pick any native input type, the keypad types numeric and decimal, or textarea; keep names the characters that survive a keystroke and reject the ones that do not, the caret staying among the survivors, and the uppercase and trim claims shape the value before it is read; v-type=number decodes the value to a number, blank staying null and a value that does not decode kept as it is, an undeclared type defaulting to number. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -455,6 +455,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -535,7 +543,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -581,6 +589,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -769,7 +785,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -815,6 +831,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -919,7 +943,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -965,6 +989,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -1069,7 +1101,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -1115,6 +1147,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -1325,12 +1365,25 @@
               "name": "caption",
               "description": "The caption of the table."
             },
+            {
+              "name": "empty",
+              "description": "Shown in place of the rows when a load returns none, replacing the localized default message."
+            },
             {
               "name": "footer",
               "description": "Content rendered in the table footer."
             }
           ],
-          "events": []
+          "events": [
+            {
+              "name": "load:success",
+              "description": "Fired once a load has settled, after the rows are in place and the busy state is gone, carrying the page response and the three requests that asked for it. Not fired for a load a newer one superseded, which owns nothing."
+            },
+            {
+              "name": "load:failure",
+              "description": "Fired when a load rejects, after the error row is shown, carrying the exception and the three requests. Telling this from an empty result is what the aria-busy attribute alone cannot do."
+            }
+          ]
         },
         {
           "name": "ful-pagination",
@@ -1404,7 +1457,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -1450,6 +1503,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -1538,7 +1599,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -1584,6 +1645,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -1672,7 +1741,7 @@
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -1718,6 +1787,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -1872,11 +1949,11 @@
         },
         {
           "name": "ful-filter-text",
-          "description": "A ful-table filter over text, with an operator such as CONTAINS or STARTS_WITH and a case sensitivity. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only. A multiple ful-select used as a filter emits the bare value array the in-list annotations expect.",
+          "description": "A ful-table filter over text, with an operator such as CONTAINS or STARTS_WITH and a case sensitivity. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
           "attributes": [
             {
               "name": "type",
-              "description": "Any native input type, or the literal textarea to render one. Defaults to number under v-type=number, and a declared type wins.",
+              "description": "Any native input type, the literal textarea to render one, or numeric and decimal, which render a text input carrying that inputmode and filter what can be typed: numeric takes digits and a leading minus, decimal one separator as well, answering it as a dot whatever the keyboard offered. Neither enforces min, max or step, which the native number type still does. Defaults to number under v-type=number, and a declared type wins.",
               "value": {
                 "kind": "plain",
                 "type": "string"
@@ -1922,6 +1999,14 @@
                 "type": "boolean"
               }
             },
+            {
+              "name": "unsigned",
+              "description": "Refuses the leading minus a numeric or decimal field otherwise takes. It narrows the type's own filter rather than replacing it, so a decimal still keeps one separator and still answers with a dot. Meaningless on any other type, where the sign is the native control's business, and a declared keep or reject still outranks it.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
             {
               "name": "autocomplete",
               "description": "The autofill token the browser classifies the control by, one of the names the html autocomplete grammar defines (name, given-name, street-address, postal-code, one-time-code, off, ...). It is set on the control itself because the control carries form=\"\", which leaves it without a form owner to inherit a form-wide setting from. Read once at the upgrade. A value outside the grammar reads as on, so an identifier of your own does not switch autofill off.",
@@ -2012,6 +2097,200 @@
             }
           ]
         },
+        {
+          "name": "ful-filter-in",
+          "description": "A ful-table filter over set membership, answering for both of data-jpa's set annotations: InEnum and InList take the same array of values and no operator, differing only in what the server converts them to. The vocabulary comes from wherever a select's does, slotted options or a loader, and the value is an array whether one key was chosen or several, an empty selection contributing nothing rather than an empty array. It picks one key unless multiple is declared, as a ful-select does.",
+          "attributes": [
+            {
+              "name": "name",
+              "description": "The field name the surrounding form submits the selection under.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "loader",
+              "description": "The registered component name the select loads its vocabulary through; loaders:select when absent.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "k-type",
+              "description": "How a key coerces when it arrives from the response or from the value attribute: number, string or bool.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "src",
+              "description": "The url the vocabulary is fetched from. Without it the slotted <option> elements are the whole vocabulary, held in memory.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "method",
+              "description": "The method the vocabulary is fetched with; POST when absent.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "mode",
+              "description": "chunked asks the endpoint per query instead of fetching the vocabulary once, for a list too large to hold.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "preload",
+              "description": "Fetches the vocabulary while the element upgrades rather than on first use. The field paints immediately either way; the options arrive when they arrive.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "revision",
+              "description": "Caches the fetched vocabulary in local storage under this revision; a load under a different one is a miss that evicts the entry. It is the cache's namespace, so a vocabulary that differs per user wants the principal in it. Left valueless, the revision the registry's 'revision' component answers is used, so a page states its build once instead of every element repeating it.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "k-expr",
+              "description": "The expression yielding an option's key, evaluated against each row of the response. Set it together with l-expr to shape a response without a mapper component.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "l-expr",
+              "description": "The expression yielding an option's label, evaluated against each row of the response.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "d-expr",
+              "description": "The expression yielding the rows from the response body; the body itself when absent.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "m-expr",
+              "description": "The expression yielding an option's metadata, evaluated against each row; the whole row when absent.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "response-mapper",
+              "description": "The registered component name that turns a response into { key, label, metadata } entries. The k-expr/l-expr pair takes precedence; without either, the response is read as positional rows.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "operator",
+              "description": "A fixed operator sent in front of the chosen keys, for the field a compare reads rather than a set: absent the value is the bare array an InEnum or an InList takes, present it is [operator, ...keys]. No menu is rendered either way, the operator being the author naming the server's comparison rather than a choice offered to whoever is filtering. The criterion reports it, so a chip can show it.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "disabled",
+              "description": "The field's own disabled claim: the control is disabled and the field is left out of the submitted values, composed with a disabled fieldset ancestry. The property reflects the claim only, matches(':disabled') tells the effective state.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "readonly",
+              "description": "Renders the control but does not let it be edited. A readonly field still contributes its value to the form.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "required",
+              "description": "Marks the field as required for assistive technologies and shows the required marker on its label.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "value",
+              "description": "Comma separated list of the selected keys. Empty contributes nothing, so the table drops the filter rather than sending an empty set.",
+              "value": {
+                "kind": "plain",
+                "type": "string"
+              }
+            },
+            {
+              "name": "multiple",
+              "description": "Always on for this element: a set of one is still a set, and a single selection would answer a bare key where the filter request wants an array.",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            },
+            {
+              "name": "item-list",
+              "description": "Shows the selection as a ful-item-list under the control as well, in addition to the field itself (the label for a single select, the ful-badge chips when multiple).",
+              "value": {
+                "kind": "plain",
+                "type": "boolean"
+              }
+            }
+          ],
+          "slots": [
+            {
+              "name": "default",
+              "description": "The label of the field."
+            },
+            {
+              "name": "info",
+              "description": "Extra content rendered next to the label, for a hint or a help icon."
+            },
+            {
+              "name": "before",
+              "description": "An addon rendered inside the input group, before the control."
+            },
+            {
+              "name": "after",
+              "description": "An addon rendered inside the input group, after the control."
+            },
+            {
+              "name": "dropdown",
+              "description": "Replaces the template used to render the options."
+            }
+          ],
+          "events": [
+            {
+              "name": "change",
+              "description": "Fired with the selected keys, or undefined when nothing is picked."
+            }
+          ]
+        },
         {
           "name": "ful-select",
           "description": "A combobox backed by a loader that acts like a select: the field mirrors the label of a single selection, clicking anywhere on it toggles the dropdown, which opens highlighting the current selection, and Home, End, PageUp, PageDown and Alt+arrows navigate it. A multiple selection renders as ful-badge chips. Without src the slotted options are the vocabulary; with src the options are fetched once (method, POST by default, preload fetching them while upgrading, revision caching them in local storage) or asked per query under mode=chunked, the response shaped through the k-expr/l-expr/d-expr/m-expr expressions or a response-mapper component, and every key coerced as k-type declares. Disabled follows native semantics: the attribute is the field's own claim, honored together with a disabled fieldset ancestry through :disabled, while the property reflects the claim only.",
@@ -2074,7 +2353,7 @@
             },
             {
               "name": "revision",
-              "description": "Caches the fetched vocabulary in local storage under this revision; a load under a different one is a miss that evicts the entry. It is the cache's namespace, so a vocabulary that differs per user wants the principal in it.",
+              "description": "Caches the fetched vocabulary in local storage under this revision; a load under a different one is a miss that evicts the entry. It is the cache's namespace, so a vocabulary that differs per user wants the principal in it. Left valueless, the revision the registry's 'revision' component answers is used, so a page states its build once instead of every element repeating it.",
               "value": {
                 "kind": "plain",
                 "type": "string"

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@optionfactory/fml",
-    "version": "9.0.0-rc10",
+    "version": "9.0.0-rc12",
     "type": "module",
     "main": "./dist/fml.mjs",
     "module": "./dist/fml.mjs",