@optionfactory/fml 9.0.0-rc1 → 9.0.0-rc11

package/dist/vscode.html-custom-data.json

@@ -3,21 +3,37 @@
   "tags": [
     {
       "name": "ful-tooltip",
-      "description": "An info affordance: a themed icon button toggling a small popover with a short explanation, opened by click and by keyboard like a button, dismissed by Escape or an outside click. placement picks the side the note sits on: bottom (default), top, left or right.",
+      "description": "An info affordance: a themed icon button toggling a small popover with a short explanation, opened by click and by keyboard like a button, dismissed by Escape or an outside click. placement picks the side the note sits on: top (default), bottom, left or right.",
       "attributes": [
         {
           "name": "placement",
-          "description": "Which side of the trigger the note opens on: bottom (the default), top, start or end. The library places the note itself on every platform, so the side is the same everywhere. (string)"
+          "description": "Which side of the trigger the note opens on: top (the default), bottom, left or right. Above by default because a note opening downwards covers the control the marker explains. The library places the note itself on every platform, so the side is the same everywhere. (string)"
+        },
+        {
+          "name": "icon",
+          "description": "The ful-icon the marker shows, for a tooltip meaning something other than plain information. Defaults to the page's Tooltip.config.icon; a name the library does not paint is declared by the page as ful-icon[name='...'] { mask-image: ... }. (string)"
+        },
+        {
+          "name": "describes",
+          "description": "For a tooltip standing in a field: the note joins the accessible description of that field's control, announced on reaching the field rather than only on opening the marker, and the marker leaves the tab order so a form of hinted fields costs no extra keystrokes to walk. The marker stays clickable, and keeps its tab stop wherever nothing took the note. (boolean)"
         }
       ]
     },
     {
       "name": "ful-dialog",
-      "description": "A modal dialog on the native platform: header, body and buttons, the header attribute naming its heading, opened by any element carrying dialog-target set to its id, or programmatically through open()/ask(), which resolve with the data-result of the button that closed the dialog (null on Escape). Longer explanations belong here, shorter ones in ful-tooltip.",
+      "description": "A modal dialog on the native platform: header, body and buttons, the header attribute naming its heading, opened by any element carrying dialog-target set to its id, or programmatically through open()/ask(), which answer with how the dialog ended, or through update(callback), which opens it on a loading state and then shows either what the callback delivered or the problems of a rejection. Longer explanations belong here, shorter ones in ful-tooltip.",
       "attributes": [
         {
           "name": "header",
           "description": "The dialog's title, shown in its header. Text only; slot content into the body instead for anything richer. (string)"
+        },
+        {
+          "name": "requires-answer",
+          "description": "For the dialog that must be answered: the close button is not rendered and Escape is refused, so the only way out is a button carrying a result. Both, since a close button withheld while Escape still worked would be decoration rather than a rule. (boolean)"
+        },
+        {
+          "name": "close-on-submit",
+          "description": "For the dialog whose answer is a form succeeding rather than a button being pressed: its own form submitting successfully closes it and answers with the response. Opt in, and its own form only, a ful-form the body holds directly, since a ful-table wraps its filters in a form of its own and searching one is not the dialog being answered. Such a dialog renders no acknowledge button of its own, the form's submit being its answer. (boolean)"
         }
       ]
     },
@@ -32,6 +48,10 @@
         {
           "name": "placement",
           "description": "Which edge the panel slides in from: end (the default) or start, following the page's writing direction. (string)"
+        },
+        {
+          "name": "close-on-submit",
+          "description": "For the drawer whose ending is a form succeeding rather than its close button being pressed: the form its content holds directly submitting successfully closes it, the close event carrying the response. Opt in, and its own form only, since a ful-table wraps its filters in a form of its own and searching one is not the drawer finishing. (boolean)"
         }
       ]
     },
@@ -106,6 +126,10 @@
         {
           "name": "scroll-on-error",
           "description": "Moves focus, and the viewport with it, to the topmost invalid field when errors land. The error live region is muted while focus moves, so each problem is announced once through the focused field rather than twice. (boolean)"
+        },
+        {
+          "name": "autocomplete",
+          "description": "The autofill token every field in the form takes unless it declares one of its own, copied onto the form element the host renders. A form cannot pass it down the way the platform would: each control carries form=\"\" so that the host is the only thing that submits, which leaves it with no form owner to inherit through, so the fields read it off the form instead. (string)"
         }
       ]
     },
@@ -137,11 +161,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -163,6 +187,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -191,7 +219,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -213,6 +241,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -297,7 +329,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -319,6 +351,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -359,7 +395,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -381,6 +417,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -421,7 +461,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -443,6 +483,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -563,7 +607,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -585,6 +629,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -617,7 +665,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -639,6 +687,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -671,7 +723,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -693,6 +745,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -747,11 +803,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. (string)"
+          "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. (string)"
         },
         {
           "name": "v-type",
@@ -773,6 +829,10 @@
           "name": "trim",
           "description": "Trims the value on the way out, leaving what was typed alone. (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. (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. (boolean)"
@@ -803,6 +863,88 @@
         }
       ]
     },
+    {
+      "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 selection is always multiple, an empty one contributing nothing rather than an empty array.",
+      "attributes": [
+        {
+          "name": "name",
+          "description": "The field name the surrounding form submits the selection under. (string)"
+        },
+        {
+          "name": "loader",
+          "description": "The registered component name the select loads its vocabulary through; loaders:select when absent. (string)"
+        },
+        {
+          "name": "k-type",
+          "description": "How a key coerces when it arrives from the response or from the value attribute: number, string or bool. (string)"
+        },
+        {
+          "name": "src",
+          "description": "The url the vocabulary is fetched from. Without it the slotted <option> elements are the whole vocabulary, held in memory. (string)"
+        },
+        {
+          "name": "method",
+          "description": "The method the vocabulary is fetched with; POST when absent. (string)"
+        },
+        {
+          "name": "mode",
+          "description": "chunked asks the endpoint per query instead of fetching the vocabulary once, for a list too large to hold. (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. (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. (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. (string)"
+        },
+        {
+          "name": "l-expr",
+          "description": "The expression yielding an option's label, evaluated against each row of the response. (string)"
+        },
+        {
+          "name": "d-expr",
+          "description": "The expression yielding the rows from the response body; the body itself when absent. (string)"
+        },
+        {
+          "name": "m-expr",
+          "description": "The expression yielding an option's metadata, evaluated against each row; the whole row when absent. (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. (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. (boolean)"
+        },
+        {
+          "name": "readonly",
+          "description": "Renders the control but does not let it be edited. A readonly field still contributes its value to the form. (boolean)"
+        },
+        {
+          "name": "required",
+          "description": "Marks the field as required for assistive technologies and shows the required marker on its label. (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. (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. (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). (boolean)"
+        }
+      ]
+    },
     {
       "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.",
@@ -837,7 +979,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. (string)"
+          "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. (string)"
         },
         {
           "name": "k-expr",