@teipublisher/pb-components 2.26.0-next-3.12 → 2.26.0-next-3.14

package/pb-elements.json

@@ -792,11 +792,11 @@
         },
         {
           "name": "pb-authority-new-entity",
-          "description": "Fiaured when user clicks the add new entity button"
+          "description": "Fired when user clicks the add new entity button"
         },
         {
           "name": "pb-authority-lookup",
-          "description": "When received, starts a lookup using the passed in query string and \nauthority type"
+          "description": "When received, starts a lookup using the passed in query string and\nauthority type"
         }
       ]
     },
@@ -1007,7 +1007,7 @@
     {
       "name": "pb-blacklab-highlight",
       "path": "./src/pb-blacklab-highlight.js",
-      "description": "This component queries the blacklab API of TEI-Publisher for a list of text matches\nin a given document. The query is given as a CQL querystring (see pattern property).\n\n**Note**: There's no demo for this component yet as it would need a blacklab instance. \n\nThe component displays 2 navigation buttons to jump to previous / next match and\na display of the current index and total number of matches.\n\nWhen navigating and the requested match is not on the current page a pb-refresh is dispatched\nto load the correct page. Once the page has dispatch pb-update this component will refresh and trigger\nloading of matches from the API.\n\nHighlighting is accomplished by marking the matched text with the following CSS classes:\n- kwic-start - for the start of the match\n- kwic-end - for the end of the match (might be on the same node as 'kwic-start'\n- kwic-current - to set a different highlight color for the current match\n\nWhen navigating the browser URL will be updated to allow bookmarks for a certain match.\n\nNote: this component does no caching of query results yet. In case of heavier use the data can be taken\nfrom localStorage ('pb-kwic-results') as usually pb-kwic-results has been visited by the user before. For\nstability reasons this was not done in this version.\n\n\nWhen data are present highlights are processed.",
+      "description": "This component queries the blacklab API of TEI-Publisher for a list of text matches\nin a given document. The query is given as a CQL querystring (see pattern property).\n\n**Note**: There's no demo for this component yet as it would need a blacklab instance.\n\nThe component displays 2 navigation buttons to jump to previous / next match and\na display of the current index and total number of matches.\n\nWhen navigating and the requested match is not on the current page a pb-refresh is dispatched\nto load the correct page. Once the page has dispatch pb-update this component will refresh and trigger\nloading of matches from the API.\n\nHighlighting is accomplished by marking the matched text with the following CSS classes:\n- kwic-start - for the start of the match\n- kwic-end - for the end of the match (might be on the same node as 'kwic-start'\n- kwic-current - to set a different highlight color for the current match\n\nWhen navigating the browser URL will be updated to allow bookmarks for a certain match.\n\nNote: this component does no caching of query results yet. In case of heavier use the data can be taken\nfrom localStorage ('pb-kwic-results') as usually pb-kwic-results has been visited by the user before. For\nstability reasons this was not done in this version.\n\n\nWhen data are present highlights are processed.",
       "attributes": [
         {
           "name": "current",
@@ -1475,7 +1475,7 @@
         },
         {
           "name": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -1678,7 +1678,7 @@
         {
           "name": "useLanguage",
           "attribute": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -1873,7 +1873,7 @@
     {
       "name": "pb-browse",
       "path": "./src/pb-browse.js",
-      "description": "Extends PbLoad to support browsing collections.\n\nThis is a reduced version of `pb-browse-docs`, which differs\nfrom a plain `pb-load` only in that it scans the returned\ncollection listing for links to subcollections and keeps\ntrack of the current collection. \n\nAll UI elements present in `pb-browse-docs` have been removed.",
+      "description": "Extends PbLoad to support browsing collections.\n\nThis is a reduced version of `pb-browse-docs`, which differs\nfrom a plain `pb-load` only in that it scans the returned\ncollection listing for links to subcollections and keeps\ntrack of the current collection.\n\nAll UI elements present in `pb-browse-docs` have been removed.",
       "attributes": [
         {
           "name": "collection",
@@ -1918,7 +1918,7 @@
         },
         {
           "name": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -2052,7 +2052,7 @@
         {
           "name": "useLanguage",
           "attribute": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -2183,7 +2183,7 @@
     {
       "name": "pb-clipboard",
       "path": "./src/pb-clipboard.js",
-      "description": "A component with a button which copies the contained content to the clipboard.\r\nUse for the typical 'quote this content as' hints on a webpage.",
+      "description": "A component with a button which copies the contained content to the clipboard.\nUse for the typical 'quote this content as' hints on a webpage.",
       "attributes": [
         {
           "name": "label",
@@ -2432,16 +2432,16 @@
         }
       ],
       "deprecated": true,
-      "deprecatedMessage": "directly use `jinn-codemirror`/`jinn-xml-editor`/`jinn-epidoc-editor` instead, which are \nincluded in the `pb-code-editor` bundle."
+      "deprecatedMessage": "directly use `jinn-codemirror`/`jinn-xml-editor`/`jinn-epidoc-editor` instead, which are\nincluded in the `pb-code-editor` bundle."
     },
     {
       "name": "pb-code-highlight",
       "path": "./src/pb-code-highlight.js",
-      "description": "Highlight a code snippet. The snippet may either be passed in a template child\r\nelement, which could contain HTML or text. If no template child is present, the\r\ncomponent will take any text content contained in it and highlight it. One can also\r\npass the code to be highlighted in the `code` property.",
+      "description": "Highlight a code snippet. The snippet may either be passed in a template child\nelement, which could contain HTML or text. If no template child is present, the\ncomponent will take any text content contained in it and highlight it. One can also\npass the code to be highlighted in the `code` property.",
       "attributes": [
         {
           "name": "code",
-          "description": "The code to be highlighted as a string. If not set,\r\nthis will be populated from either a template child element\r\nor the element's text content.\r\nThe value of the property can be changed programmatically from JavaScript.",
+          "description": "The code to be highlighted as a string. If not set,\nthis will be populated from either a template child element\nor the element's text content.\nThe value of the property can be changed programmatically from JavaScript.",
           "type": "string"
         },
         {
@@ -2452,7 +2452,7 @@
         },
         {
           "name": "theme",
-          "description": "Highlighting theme to use: 'coy', 'dark', 'funky', 'okaida', 'solarizedlight',\r\n'tomorrow', 'twilight' or 'default'.",
+          "description": "Highlighting theme to use: 'coy', 'dark', 'funky', 'okaida', 'solarizedlight',\n'tomorrow', 'twilight' or 'default'.",
           "type": "string",
           "default": "\"default\""
         },
@@ -2466,7 +2466,7 @@
         {
           "name": "code",
           "attribute": "code",
-          "description": "The code to be highlighted as a string. If not set,\r\nthis will be populated from either a template child element\r\nor the element's text content.\r\nThe value of the property can be changed programmatically from JavaScript.",
+          "description": "The code to be highlighted as a string. If not set,\nthis will be populated from either a template child element\nor the element's text content.\nThe value of the property can be changed programmatically from JavaScript.",
           "type": "string"
         },
         {
@@ -2479,7 +2479,7 @@
         {
           "name": "theme",
           "attribute": "theme",
-          "description": "Highlighting theme to use: 'coy', 'dark', 'funky', 'okaida', 'solarizedlight',\r\n'tomorrow', 'twilight' or 'default'.",
+          "description": "Highlighting theme to use: 'coy', 'dark', 'funky', 'okaida', 'solarizedlight',\n'tomorrow', 'twilight' or 'default'.",
           "type": "string",
           "default": "\"default\""
         },
@@ -2753,7 +2753,7 @@
     {
       "name": "pb-combo-box",
       "path": "./src/pb-combo-box.js",
-      "description": "Provides a combo box, i.e. a combination of an input with a dropdown.\nItems to select from may be obtained from a remote data source.\n\nThe form control to be used (either a select or input) should be passed \nin the content of the element. If no control is provided, a simple `<input>`\nwill be created.",
+      "description": "Provides a combo box, i.e. a combination of an input with a dropdown.\nItems to select from may be obtained from a remote data source.\n\nThe form control to be used (either a select or input) should be passed\nin the content of the element. If no control is provided, a simple `<input>`\nwill be created.",
       "attributes": [
         {
           "name": "source",
@@ -2964,7 +2964,7 @@
         },
         {
           "name": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -3091,7 +3091,7 @@
         {
           "name": "useLanguage",
           "attribute": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -3234,7 +3234,7 @@
     {
       "name": "pb-dialog",
       "path": "./src/pb-dialog.js",
-      "description": "A simple dialog component using the HTML5 <dialog> element",
+      "description": "A simple dialog component using the HTML5 <dialog> element.\n\nAny button with the attribute `rel=\"prev\"` will close the dialog when clicked.",
       "attributes": [
         {
           "name": "open",
@@ -3524,7 +3524,7 @@
       "attributes": [
         {
           "name": "src",
-          "description": "optional id reference to a pb-document. If `url` is not specified, \na correct download URL is constructed using the given document path and parameters.\nOtherwise `url` will be used as main URL.",
+          "description": "optional id reference to a pb-document. If `url` is not specified,\na correct download URL is constructed using the given document path and parameters.\nOtherwise `url` will be used as main URL.",
           "type": "string"
         },
         {
@@ -3600,7 +3600,7 @@
         {
           "name": "src",
           "attribute": "src",
-          "description": "optional id reference to a pb-document. If `url` is not specified, \na correct download URL is constructed using the given document path and parameters.\nOtherwise `url` will be used as main URL.",
+          "description": "optional id reference to a pb-document. If `url` is not specified,\na correct download URL is constructed using the given document path and parameters.\nOtherwise `url` will be used as main URL.",
           "type": "string"
         },
         {
@@ -4133,7 +4133,7 @@
         },
         {
           "name": "trigger",
-          "description": "Type of event which should trigger the facsimile to display. \nEither 'click' or 'mouseover' (default).",
+          "description": "Type of event which should trigger the facsimile to display.\nEither 'click' or 'mouseover' (default).",
           "type": "string",
           "default": "\"mouseover\""
         },
@@ -4202,7 +4202,7 @@
         {
           "name": "trigger",
           "attribute": "trigger",
-          "description": "Type of event which should trigger the facsimile to display. \nEither 'click' or 'mouseover' (default).",
+          "description": "Type of event which should trigger the facsimile to display.\nEither 'click' or 'mouseover' (default).",
           "type": "string",
           "default": "\"mouseover\""
         },
@@ -4689,7 +4689,7 @@
     {
       "name": "pb-geolocation",
       "path": "./src/pb-geolocation.js",
-      "description": "Represents a geo location. Extends `pb-highlight`, but sends an additional `pb-geolocation` event\non mouseover.\n\nFor `pb-leaflet-map` to show markers for `pb-geolocation` elements, make sure that map subscribes to the channel\ninto which `pb-geolocation`s emit and that map is loaded before the emitting component, e.g. `pb-view`, by specifying \n`wait-for` property.",
+      "description": "Represents a geo location. Extends `pb-highlight`, but sends an additional `pb-geolocation` event\non mouseover.\n\nFor `pb-leaflet-map` to show markers for `pb-geolocation` elements, make sure that map subscribes to the channel\ninto which `pb-geolocation`s emit and that map is loaded before the emitting component, e.g. `pb-view`, by specifying\n`wait-for` property.",
       "attributes": [
         {
           "name": "longitude",
@@ -5695,7 +5695,7 @@
         },
         {
           "name": "geo-coding",
-          "description": "Enables geocoding: an additional control will allow users to search for a place.\nReverse geocoding is also possible: clicking on the map while pressing ctrl or cmd \nwill request information about the current location.\n\nIn both cases, a `pb-geocode` event will be emitted containing additional information\nabout the place in the event details (see demo).\n\nFor lookups the free OSM/Nominatim service is used.",
+          "description": "Enables geocoding: an additional control will allow users to search for a place.\nReverse geocoding is also possible: clicking on the map while pressing ctrl or cmd\nwill request information about the current location.\n\nIn both cases, a `pb-geocode` event will be emitted containing additional information\nabout the place in the event details (see demo).\n\nFor lookups the free OSM/Nominatim service is used.",
           "type": "boolean",
           "default": "false"
         },
@@ -5815,7 +5815,7 @@
         {
           "name": "geoCoding",
           "attribute": "geo-coding",
-          "description": "Enables geocoding: an additional control will allow users to search for a place.\nReverse geocoding is also possible: clicking on the map while pressing ctrl or cmd \nwill request information about the current location.\n\nIn both cases, a `pb-geocode` event will be emitted containing additional information\nabout the place in the event details (see demo).\n\nFor lookups the free OSM/Nominatim service is used.",
+          "description": "Enables geocoding: an additional control will allow users to search for a place.\nReverse geocoding is also possible: clicking on the map while pressing ctrl or cmd\nwill request information about the current location.\n\nIn both cases, a `pb-geocode` event will be emitted containing additional information\nabout the place in the event details (see demo).\n\nFor lookups the free OSM/Nominatim service is used.",
           "type": "boolean",
           "default": "false"
         },
@@ -5889,7 +5889,7 @@
     {
       "name": "pb-link",
       "path": "./src/pb-link.js",
-      "description": "Create an internal link: clicking it will emit a `pb-refresh`event, \ncausing connected views to update and load the corresponding document fragment defined by the\nproperties.",
+      "description": "Create an internal link: clicking it will emit a `pb-refresh`event,\ncausing connected views to update and load the corresponding document fragment defined by the\nproperties.",
       "attributes": [
         {
           "name": "xml-id",
@@ -6106,7 +6106,7 @@
         },
         {
           "name": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -6227,7 +6227,7 @@
         {
           "name": "useLanguage",
           "attribute": "use-language",
-          "description": "If set, a parameter \"language\" will be added to the parameter list. \nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
+          "description": "If set, a parameter \"language\" will be added to the parameter list.\nAlso, a refresh will be triggered if a `pb-i18n-update` event is received,\ne.g. due to the user selecting a different interface language.\n\nAlso requires `requireLanguage` to be set on the surrounding `pb-page`.\nSee there for more information.",
           "type": "boolean"
         },
         {
@@ -6698,7 +6698,7 @@
     {
       "name": "pb-map-icon",
       "path": "./src/pb-map-icon.js",
-      "description": "Configure a map icon type to be used for markers. \nShould be nested inside `pb-leaflet-map`.",
+      "description": "Configure a map icon type to be used for markers.\nShould be nested inside `pb-leaflet-map`.",
       "attributes": [
         {
           "name": "icon-size",
@@ -7091,7 +7091,7 @@
     {
       "name": "pb-mei",
       "path": "./src/pb-mei.js",
-      "description": "A viewer and player for MEI musical notation based on [Verovio](https://www.verovio.org/).\nSupports optional MIDI playback using [web-midi-player](https://midi.yvesgurcan.com/).\nBoth libraries are loaded dynamically when the component is used the first time.\n\nViewing options to be selected by the user can be defined via nested `pb-option` elements:\n\n```html\n<pb-mei id=\"viewer\" player url=\"http://www.marenzio.org/mei/M-06-5/M_06_5_01_S_io_parto_i_moro_e_pur_partir_conviene.mei\" \n        footer=\"none\">\n   <pb-option name=\"appXPath\" on=\"./rdg[contains(@label, 'original')]\" off=\"\">Original Clefs</pb-option>\n</pb-mei>\n```\n\nThe MEI document to display can either be given directly in the `data` property or loaded from an URL\nspecified in `url`.",
+      "description": "A viewer and player for MEI musical notation based on [Verovio](https://www.verovio.org/).\nSupports optional MIDI playback using [web-midi-player](https://midi.yvesgurcan.com/).\nBoth libraries are loaded dynamically when the component is used the first time.\n\nViewing options to be selected by the user can be defined via nested `pb-option` elements:\n\n```html\n<pb-mei id=\"viewer\" player url=\"http://www.marenzio.org/mei/M-06-5/M_06_5_01_S_io_parto_i_moro_e_pur_partir_conviene.mei\"\n        footer=\"none\">\n   <pb-option name=\"appXPath\" on=\"./rdg[contains(@label, 'original')]\" off=\"\">Original Clefs</pb-option>\n</pb-mei>\n```\n\nThe MEI document to display can either be given directly in the `data` property or loaded from an URL\nspecified in `url`.",
       "attributes": [
         {
           "name": "data",
@@ -7100,7 +7100,7 @@
         },
         {
           "name": "url",
-          "description": "URL of the MEI file to load. Will be used if no `data` property is present. \nA relative URL would be resolved relative to the TEI Publisher endpoint.",
+          "description": "URL of the MEI file to load. Will be used if no `data` property is present.\nA relative URL would be resolved relative to the TEI Publisher endpoint.",
           "type": "string"
         },
         {
@@ -7188,7 +7188,7 @@
         {
           "name": "url",
           "attribute": "url",
-          "description": "URL of the MEI file to load. Will be used if no `data` property is present. \nA relative URL would be resolved relative to the TEI Publisher endpoint.",
+          "description": "URL of the MEI file to load. Will be used if no `data` property is present.\nA relative URL would be resolved relative to the TEI Publisher endpoint.",
           "type": "string"
         },
         {
@@ -8480,7 +8480,7 @@
         },
         {
           "name": "locales",
-          "description": "Optional URL pointing to a directory from which additional i18n \nlanguage files will be loaded. The URL should contain placeholders\nfor the language (`lng`) and the namespace (`ns`), e.g.\n\n`resources/i18n/{{ns}}_{{lng}}.json`\n\nor\n\n`resources/i18n/{{ns}}/{{lng}}.json`\n\nThe latter assumes custom language files in a subdirectory, the first\nexpects the namespace to be specified at the start of the file name.\n\nThe default namespace for custom language files is assumed to be `app`,\nbut you can define additional namespaces via `localeFallbackNS`.",
+          "description": "Optional URL pointing to a directory from which additional i18n\nlanguage files will be loaded. The URL should contain placeholders\nfor the language (`lng`) and the namespace (`ns`), e.g.\n\n`resources/i18n/{{ns}}_{{lng}}.json`\n\nor\n\n`resources/i18n/{{ns}}/{{lng}}.json`\n\nThe latter assumes custom language files in a subdirectory, the first\nexpects the namespace to be specified at the start of the file name.\n\nThe default namespace for custom language files is assumed to be `app`,\nbut you can define additional namespaces via `localeFallbackNS`.",
           "type": "string"
         },
         {
@@ -8507,7 +8507,7 @@
         },
         {
           "name": "url-template",
-          "description": "Can be used to define parameters which should be serialized in the\nURL path rather than as query parameters. Expects a url pattern\nrelative to the application root\n(supported patterns are documented in the \n[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) library documentation).\n\nFor example, a pattern `:lang/texts/:path/:id?` would support URLs like \n`en/texts/text1/chapter1`. Whenever components change state – e.g. due to a navigation\nevent – the standard parameters `path`, `lang` and `id` would be serialized into the\nURL path pattern rather than query parameters.",
+          "description": "Can be used to define parameters which should be serialized in the\nURL path rather than as query parameters. Expects a url pattern\nrelative to the application root\n(supported patterns are documented in the\n[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) library documentation).\n\nFor example, a pattern `:lang/texts/:path/:id?` would support URLs like\n`en/texts/text1/chapter1`. Whenever components change state – e.g. due to a navigation\nevent – the standard parameters `path`, `lang` and `id` would be serialized into the\nURL path pattern rather than query parameters.",
           "type": "string"
         },
         {
@@ -8534,7 +8534,7 @@
         },
         {
           "name": "require-language",
-          "description": "If set, the element will wait for a language being set by i18n before\nit sends a `pb-page-ready` event. Elements like `pb-view` will wait\nfor this event before displaying content.\n\nAlso, `pb-view` will pass the configured language to the server endpoint\nwhere it will be available to ODD processing models in variable \n`$parameters?language` and can thus be used to change output depending on\nthe user interface language.\n\nIf you would like `pb-view` to refresh automatically whenever the language\nsetting changes, specify property `useLanguage` on the corresponding `pb-view`.",
+          "description": "If set, the element will wait for a language being set by i18n before\nit sends a `pb-page-ready` event. Elements like `pb-view` will wait\nfor this event before displaying content.\n\nAlso, `pb-view` will pass the configured language to the server endpoint\nwhere it will be available to ODD processing models in variable\n`$parameters?language` and can thus be used to change output depending on\nthe user interface language.\n\nIf you would like `pb-view` to refresh automatically whenever the language\nsetting changes, specify property `useLanguage` on the corresponding `pb-view`.",
           "type": "boolean",
           "default": "false"
         },
@@ -8601,7 +8601,7 @@
         {
           "name": "locales",
           "attribute": "locales",
-          "description": "Optional URL pointing to a directory from which additional i18n \nlanguage files will be loaded. The URL should contain placeholders\nfor the language (`lng`) and the namespace (`ns`), e.g.\n\n`resources/i18n/{{ns}}_{{lng}}.json`\n\nor\n\n`resources/i18n/{{ns}}/{{lng}}.json`\n\nThe latter assumes custom language files in a subdirectory, the first\nexpects the namespace to be specified at the start of the file name.\n\nThe default namespace for custom language files is assumed to be `app`,\nbut you can define additional namespaces via `localeFallbackNS`.",
+          "description": "Optional URL pointing to a directory from which additional i18n\nlanguage files will be loaded. The URL should contain placeholders\nfor the language (`lng`) and the namespace (`ns`), e.g.\n\n`resources/i18n/{{ns}}_{{lng}}.json`\n\nor\n\n`resources/i18n/{{ns}}/{{lng}}.json`\n\nThe latter assumes custom language files in a subdirectory, the first\nexpects the namespace to be specified at the start of the file name.\n\nThe default namespace for custom language files is assumed to be `app`,\nbut you can define additional namespaces via `localeFallbackNS`.",
           "type": "string"
         },
         {
@@ -8637,7 +8637,7 @@
         {
           "name": "urlTemplate",
           "attribute": "url-template",
-          "description": "Can be used to define parameters which should be serialized in the\nURL path rather than as query parameters. Expects a url pattern\nrelative to the application root\n(supported patterns are documented in the \n[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) library documentation).\n\nFor example, a pattern `:lang/texts/:path/:id?` would support URLs like \n`en/texts/text1/chapter1`. Whenever components change state – e.g. due to a navigation\nevent – the standard parameters `path`, `lang` and `id` would be serialized into the\nURL path pattern rather than query parameters.",
+          "description": "Can be used to define parameters which should be serialized in the\nURL path rather than as query parameters. Expects a url pattern\nrelative to the application root\n(supported patterns are documented in the\n[path-to-regexp](https://www.npmjs.com/package/path-to-regexp) library documentation).\n\nFor example, a pattern `:lang/texts/:path/:id?` would support URLs like\n`en/texts/text1/chapter1`. Whenever components change state – e.g. due to a navigation\nevent – the standard parameters `path`, `lang` and `id` would be serialized into the\nURL path pattern rather than query parameters.",
           "type": "string"
         },
         {
@@ -8669,7 +8669,7 @@
         {
           "name": "requireLanguage",
           "attribute": "require-language",
-          "description": "If set, the element will wait for a language being set by i18n before\nit sends a `pb-page-ready` event. Elements like `pb-view` will wait\nfor this event before displaying content.\n\nAlso, `pb-view` will pass the configured language to the server endpoint\nwhere it will be available to ODD processing models in variable \n`$parameters?language` and can thus be used to change output depending on\nthe user interface language.\n\nIf you would like `pb-view` to refresh automatically whenever the language\nsetting changes, specify property `useLanguage` on the corresponding `pb-view`.",
+          "description": "If set, the element will wait for a language being set by i18n before\nit sends a `pb-page-ready` event. Elements like `pb-view` will wait\nfor this event before displaying content.\n\nAlso, `pb-view` will pass the configured language to the server endpoint\nwhere it will be available to ODD processing models in variable\n`$parameters?language` and can thus be used to change output depending on\nthe user interface language.\n\nIf you would like `pb-view` to refresh automatically whenever the language\nsetting changes, specify property `useLanguage` on the corresponding `pb-view`.",
           "type": "boolean",
           "default": "false"
         },
@@ -9122,7 +9122,7 @@
     {
       "name": "pb-popover",
       "path": "./src/pb-popover.js",
-      "description": "Show a popover. It may either \n\n1. be attached to another element on the page which serves as a trigger. For this the\n`for` property must be specified and should contain the ID of the trigger element. \nThe whole content of the `pb-popover` element will be shown in the popup.\n\n2. if no `for` property is specified, the `pb-popover` acts itself as the trigger. The trigger\ntext is either taken from a slot named `default` - or the default slot (i.e. the content of the element).\nThe content to show in the popup should be supplied in a slot named `alternate`. It is recommended to use an\nHTML `template` to specify the alternate, so it is ignored by the browser:\n\n```html\n<pb-popover theme=\"material\">\n     <span slot=\"default\">ipsum dolor sit amet</span>\n     <template slot=\"alternate\">\n         <p>At vero eos et <strong>accusam</strong> et justo duo dolores<br>\n         et ea rebum.</p>\n     </template>\n</pb-popover>\n```\n\nIf you would like popovers to contain nested popovers, choose approach 1 above and use `for`.\n\nIf property `persistent` is true, the popover will be shown\non click. Otherwise display a tooltip on mouseover.\n\n`pb-popover` uses the tippy.js library for the popup.\n\n## Styling\n\nWhen showing the popup, the popup content will either be added to the parent shadow DOM - if the `pb-popover`\nis located inside the shadow DOM of another element like `pb-view`; or the document body. This has an\neffect on where CSS styles can be defined: within a `pb-view`, only the styles specified inside the\nCSS attached to the ODD are applied.",
+      "description": "Show a popover. It may either\n\n1. be attached to another element on the page which serves as a trigger. For this the\n`for` property must be specified and should contain the ID of the trigger element.\nThe whole content of the `pb-popover` element will be shown in the popup.\n\n2. if no `for` property is specified, the `pb-popover` acts itself as the trigger. The trigger\ntext is either taken from a slot named `default` - or the default slot (i.e. the content of the element).\nThe content to show in the popup should be supplied in a slot named `alternate`. It is recommended to use an\nHTML `template` to specify the alternate, so it is ignored by the browser:\n\n```html\n<pb-popover theme=\"material\">\n     <span slot=\"default\">ipsum dolor sit amet</span>\n     <template slot=\"alternate\">\n         <p>At vero eos et <strong>accusam</strong> et justo duo dolores<br>\n         et ea rebum.</p>\n     </template>\n</pb-popover>\n```\n\nIf you would like popovers to contain nested popovers, choose approach 1 above and use `for`.\n\nIf property `persistent` is true, the popover will be shown\non click. Otherwise display a tooltip on mouseover.\n\n`pb-popover` uses the tippy.js library for the popup.\n\n## Styling\n\nWhen showing the popup, the popup content will either be added to the parent shadow DOM - if the `pb-popover`\nis located inside the shadow DOM of another element like `pb-view`; or the document body. This has an\neffect on where CSS styles can be defined: within a `pb-view`, only the styles specified inside the\nCSS attached to the ODD are applied.",
       "attributes": [
         {
           "name": "remote",
@@ -9506,7 +9506,7 @@
     {
       "name": "pb-progress",
       "path": "./src/pb-progress.js",
-      "description": "A progress bar which becomes active when signal `pb-start-update` is\nbeing sent and is deactivated on `pb-end-update`.",
+      "description": "A progress bar which becomes active when signal `pb-start-update` is\nbeing sent and is deactivated on `pb-end-update`.\n\nUses a native `<progress>` element.",
       "attributes": [
         {
           "name": "subscribe",
@@ -10045,7 +10045,7 @@
     {
       "name": "pb-select-feature",
       "path": "./src/pb-select-feature.js",
-      "description": "Similar to `pb-toggle-feature` but allows you to choose from a list of defined states instead of a simple\non/off toggle. Like `pb-toggle-feature` it can change state server-side as well as client-side. \n\nThe list of states is passed as a JSON array to property `items`:\n\n# Server-side\n\nProperties to be passed to the server are specified as follows:\n\n```javascript\n[\n     {\"name\": \"Diplomatic View\", \"properties\": {\"mode\": \"diplomatic\", \"view\": \"page\"}},\n     {\"name\": \"Normalized View\", \"properties\": {\"mode\": \"norm\", \"view\": \"single\"}}\n]\n```\n\nIf the `name` property references the path to a translated label, the translation will be used instead.\n# Client-side\n\n```javascript\n[\n     {\"name\": \"Diplomatic View\", \"selectors\": [{\"selector\": \".choice,.choice-alternate,br\", \"state\": false},{\"selector\": \".tei-foreign,pb-highlight,pb-popover\", \"command\": \"disable\"}]},\n     {\"name\": \"Normalized View\", \"selectors\": [{\"selector\": \".choice,.choice-alternate,br\", \"state\": true},{\"selector\": \".tei-foreign,pb-highlight,pb-popover\", \"command\": \"disable\"}]},\n     {\"name\": \"Plain Reading View\", \"selectors\": [{\"selector\": \".choice,.choice-alternate,br\", \"state\": true}, {\"selector\": \".tei-foreign,pb-highlight,pb-popover\", \"command\": \"disable\", \"state\": true}]}\n]\n```\n\nEach item in the `selectors` property above defines either a state or a command. *state* will simply add\na css class `.toggle` to the target element when true. If *command* is set to 'disable', it will entirely disable\nthe functionality of selected elements - provided that they are\npublisher components implementing the corresponding `command` method of `pb-mixin`.\n\nClient-side you may also pass an optional property `\"global\": true` to toggle the state of elements which reside\nin the surrounding HTML context below `pb-page` (means: elements which are not inside a `pb-view` or `pb-load`).",
+      "description": "Similar to `pb-toggle-feature` but allows you to choose from a list of defined states instead of a simple\non/off toggle. Like `pb-toggle-feature` it can change state server-side as well as client-side.\n\nThe list of states is passed as a JSON array to property `items`:\n\n# Server-side\n\nProperties to be passed to the server are specified as follows:\n\n```javascript\n[\n     {\"name\": \"Diplomatic View\", \"properties\": {\"mode\": \"diplomatic\", \"view\": \"page\"}},\n     {\"name\": \"Normalized View\", \"properties\": {\"mode\": \"norm\", \"view\": \"single\"}}\n]\n```\n\nIf the `name` property references the path to a translated label, the translation will be used instead.\n# Client-side\n\n```javascript\n[\n     {\"name\": \"Diplomatic View\", \"selectors\": [{\"selector\": \".choice,.choice-alternate,br\", \"state\": false},{\"selector\": \".tei-foreign,pb-highlight,pb-popover\", \"command\": \"disable\"}]},\n     {\"name\": \"Normalized View\", \"selectors\": [{\"selector\": \".choice,.choice-alternate,br\", \"state\": true},{\"selector\": \".tei-foreign,pb-highlight,pb-popover\", \"command\": \"disable\"}]},\n     {\"name\": \"Plain Reading View\", \"selectors\": [{\"selector\": \".choice,.choice-alternate,br\", \"state\": true}, {\"selector\": \".tei-foreign,pb-highlight,pb-popover\", \"command\": \"disable\", \"state\": true}]}\n]\n```\n\nEach item in the `selectors` property above defines either a state or a command. *state* will simply add\na css class `.toggle` to the target element when true. If *command* is set to 'disable', it will entirely disable\nthe functionality of selected elements - provided that they are\npublisher components implementing the corresponding `command` method of `pb-mixin`.\n\nClient-side you may also pass an optional property `\"global\": true` to toggle the state of elements which reside\nin the surrounding HTML context below `pb-page` (means: elements which are not inside a `pb-view` or `pb-load`).",
       "attributes": [
         {
           "name": "name",
@@ -10578,7 +10578,7 @@
     {
       "name": "pb-split-list",
       "path": "./src/pb-split-list.js",
-      "description": "Implements a list which is split into different categories \n(e.g. letters of the alphabet, countries ...).\nOnly one category is shown at a time unless the server reports\nno categories (e.g. if the number of items to display goes below\na defined threshold).\n\nThe server-side API endpoint should return a JSON object with two\nproperties:\n\n+ `categories`: an array of category descriptions: each item should \n be an object with two properties: `category` - containing the name of the category\n and `count` - containing a count of items available under this category.\n+ `items`: an array with the items to be shown for the currently selected\n category. Those may contain HTML markup.\n\nSample JSON object for pb-split-list\n```javascript\n{\n   \"items\": [\n       \"<span><a href='Abegg-Arter Carl?category=A&amp;view=correspondents&amp;search='>Abegg-Arter, Carl</a><span class='dates'> (1836–1912)</span></span>\",\n       \"<span><a href='Abegg Hans Heinrich?category=A&amp;view=correspondents&amp;search='>Abegg, Hans Heinrich</a><span class='dates'> (1805–1874)</span></span>\",\n       \"<span><a href='Abegg Jakob?category=A&amp;view=correspondents&amp;search='>Abegg, Jakob</a><span class='dates'> (1801–1871)</span></span>\",\n       \"<span><a href='Abys Raget?category=A&amp;view=correspondents&amp;search='>Abys, Raget</a><span class='dates'> (1790–1861)</span></span>\",\n       \"<span><a href='Aebli Johann Peter?category=A&amp;view=correspondents&amp;search='>Aebli, Johann Peter</a><span class='dates'> (1804–1879)</span></span>\",\n       \"<span><a href='Aepli Arnold Otto?category=A&amp;view=correspondents&amp;search='>Aepli, Arnold Otto</a><span class='dates'> (1816–1897)</span></span>\",\n       ...\n   ],\n   \"categories\": [\n       {\n           \"category\": \"A\",\n           \"count\": 22\n       },\n       {\n           \"category\": \"B\",\n           \"count\": 77\n       },\n       {\n           \"category\": \"C\",\n           \"count\": 19\n       },\n     ...\n   ]\n}\n```\n\nSample Usage \n```xml\n<pb-split-list url=\"api/people\" subforms=\"#options\" selected=\"A\" emit=\"transcription\" subscribe=\"transcription\"></pb-split-list>\n```\nSee https://www.briefedition.alfred-escher.ch/kontexte/personen/?category=A&search=&view=correspondents for a running sample. The source code of the webpage is here: https://github.com/stazh/briefedition-escher. Relevant files are: \n- [templates/index.html](https://github.com/stazh/briefedition-escher/blob/master/templates/index.html#L223) - usage of pb-timeline\n- [modules/custom-api.json](https://github.com/stazh/briefedition-escher/blob/master/modules/custom-api.json#L1098) - `/api/people` endpoint delivering required JSON object",
+      "description": "Implements a list which is split into different categories\n(e.g. letters of the alphabet, countries ...).\nOnly one category is shown at a time unless the server reports\nno categories (e.g. if the number of items to display goes below\na defined threshold).\n\nThe server-side API endpoint should return a JSON object with two\nproperties:\n\n+ `categories`: an array of category descriptions: each item should\n be an object with two properties: `category` - containing the name of the category\n and `count` - containing a count of items available under this category.\n+ `items`: an array with the items to be shown for the currently selected\n category. Those may contain HTML markup.\n\nSample JSON object for pb-split-list\n```javascript\n{\n   \"items\": [\n       \"<span><a href='Abegg-Arter Carl?category=A&amp;view=correspondents&amp;search='>Abegg-Arter, Carl</a><span class='dates'> (1836–1912)</span></span>\",\n       \"<span><a href='Abegg Hans Heinrich?category=A&amp;view=correspondents&amp;search='>Abegg, Hans Heinrich</a><span class='dates'> (1805–1874)</span></span>\",\n       \"<span><a href='Abegg Jakob?category=A&amp;view=correspondents&amp;search='>Abegg, Jakob</a><span class='dates'> (1801–1871)</span></span>\",\n       \"<span><a href='Abys Raget?category=A&amp;view=correspondents&amp;search='>Abys, Raget</a><span class='dates'> (1790–1861)</span></span>\",\n       \"<span><a href='Aebli Johann Peter?category=A&amp;view=correspondents&amp;search='>Aebli, Johann Peter</a><span class='dates'> (1804–1879)</span></span>\",\n       \"<span><a href='Aepli Arnold Otto?category=A&amp;view=correspondents&amp;search='>Aepli, Arnold Otto</a><span class='dates'> (1816–1897)</span></span>\",\n       ...\n   ],\n   \"categories\": [\n       {\n           \"category\": \"A\",\n           \"count\": 22\n       },\n       {\n           \"category\": \"B\",\n           \"count\": 77\n       },\n       {\n           \"category\": \"C\",\n           \"count\": 19\n       },\n     ...\n   ]\n}\n```\n\nSample Usage\n```xml\n<pb-split-list url=\"api/people\" subforms=\"#options\" selected=\"A\" emit=\"transcription\" subscribe=\"transcription\"></pb-split-list>\n```\nSee https://www.briefedition.alfred-escher.ch/kontexte/personen/?category=A&search=&view=correspondents for a running sample. The source code of the webpage is here: https://github.com/stazh/briefedition-escher. Relevant files are:\n- [templates/index.html](https://github.com/stazh/briefedition-escher/blob/master/templates/index.html#L223) - usage of pb-timeline\n- [modules/custom-api.json](https://github.com/stazh/briefedition-escher/blob/master/modules/custom-api.json#L1098) - `/api/people` endpoint delivering required JSON object",
       "attributes": [
         {
           "name": "url",
@@ -11117,7 +11117,7 @@
       "events": [
         {
           "name": "pb-tab",
-          "description": "fired if selected tab changes. Details contain number of \nselected tab in propery `selected`."
+          "description": "fired if selected tab changes. Details contain number of\nselected tab in propery `selected`."
         }
       ],
       "slots": [
@@ -11243,7 +11243,7 @@
     {
       "name": "pb-timeline",
       "path": "./src/pb-timeline.js",
-      "description": "A timeline component to display time series data in a bar chart like view.\n\nTime series data can be displayed in one of 6 different scales:\n\n- by decade (10Y)\n- by 5 years (5Y)\n- by years (Y)\n- by month (M)\n- by week (W)\n- by day (D)\n\nThe endpoint is expected to return a JSON object. Each property should either be a date or the special\nmarker `?`, which indicates undated resources.\nThe value associated with each entry\nshould either correspond to a count of resources or an object with properties `count` and `info`. \n`info` should be an array, containing HTML to be shown in a list within the tooltips.\nExpected JSON: \n```javascript\n{\n \"1852-01-14\": {\n     \"count\": 1,\n     \"info\": [\n       \"<a href='/briefe/B0977' part='tooltip-link'>Alfred Escher an Joseph Wolfgang von Deschwanden, Belvoir (Enge, Zürich), Mittwoch, 14. Januar 1852</a>\"\n    ]\n  },\n\"1874-01-25\": {\n   \"count\": 3,\n    \"info\": [\n        \"<a href='/briefe/B8140' part='tooltip-link'>Alfred Escher an Gustav von Mevissen, Zürich, Sonntag, 25. Januar 1874</a>\",\n        \"<a href='/briefe/B8139' part='tooltip-link'>Alfred Escher an Theodor Weishaupt, Zürich, Sonntag, 25. Januar 1874</a>\",\n        \"<a href='/briefe/B8143' part='tooltip-link'>Alfred Escher an Ludwig August Parcus, Zürich, Sonntag, 25. Januar 1874</a>\"\n    ]\n }\n}\n```\nSample Usage:\n```xml\n<pb-timeline url=\"api/timeline\" scopes=\"['D', 'M', 'Y', '5Y', '10Y']\"\n     resettable=\"\"\n     subscribe=\"docs\" emit=\"timeline\">\n  <span slot=\"label\">Angezeigter Zeitraum: </span>\n</pb-timeline>\n```\nSee https://www.briefedition.alfred-escher.ch/briefe/ for a running sample. The source code of the webpage is here: https://github.com/stazh/briefedition-escher. Relevant files are: \n- [templates/people.html](https://github.com/stazh/briefedition-escher/blob/master/templates/people.html#L91) - usage of pb-timeline\n- [modules/custom-api.json](https://github.com/stazh/briefedition-escher/blob/master/modules/custom-api.json#L1080) - `/api/timeline` endpoint delivering required JSON object",
+      "description": "A timeline component to display time series data in a bar chart like view.\n\nTime series data can be displayed in one of 6 different scales:\n\n- by decade (10Y)\n- by 5 years (5Y)\n- by years (Y)\n- by month (M)\n- by week (W)\n- by day (D)\n\nThe endpoint is expected to return a JSON object. Each property should either be a date or the special\nmarker `?`, which indicates undated resources.\nThe value associated with each entry\nshould either correspond to a count of resources or an object with properties `count` and `info`.\n`info` should be an array, containing HTML to be shown in a list within the tooltips.\nExpected JSON:\n```javascript\n{\n \"1852-01-14\": {\n     \"count\": 1,\n     \"info\": [\n       \"<a href='/briefe/B0977' part='tooltip-link'>Alfred Escher an Joseph Wolfgang von Deschwanden, Belvoir (Enge, Zürich), Mittwoch, 14. Januar 1852</a>\"\n    ]\n  },\n\"1874-01-25\": {\n   \"count\": 3,\n    \"info\": [\n        \"<a href='/briefe/B8140' part='tooltip-link'>Alfred Escher an Gustav von Mevissen, Zürich, Sonntag, 25. Januar 1874</a>\",\n        \"<a href='/briefe/B8139' part='tooltip-link'>Alfred Escher an Theodor Weishaupt, Zürich, Sonntag, 25. Januar 1874</a>\",\n        \"<a href='/briefe/B8143' part='tooltip-link'>Alfred Escher an Ludwig August Parcus, Zürich, Sonntag, 25. Januar 1874</a>\"\n    ]\n }\n}\n```\nSample Usage:\n```xml\n<pb-timeline url=\"api/timeline\" scopes=\"['D', 'M', 'Y', '5Y', '10Y']\"\n     resettable=\"\"\n     subscribe=\"docs\" emit=\"timeline\">\n  <span slot=\"label\">Angezeigter Zeitraum: </span>\n</pb-timeline>\n```\nSee https://www.briefedition.alfred-escher.ch/briefe/ for a running sample. The source code of the webpage is here: https://github.com/stazh/briefedition-escher. Relevant files are:\n- [templates/people.html](https://github.com/stazh/briefedition-escher/blob/master/templates/people.html#L91) - usage of pb-timeline\n- [modules/custom-api.json](https://github.com/stazh/briefedition-escher/blob/master/modules/custom-api.json#L1080) - `/api/timeline` endpoint delivering required JSON object",
       "attributes": [
         {
           "name": "start-date",

package/src/assets/components.css

@@ -1,5 +1,5 @@
-/*
- * Global component theme stylesheet
- * 
- * Styles defined here are injected into a components' shadow DOM.
- */
+/*
+ * Global component theme stylesheet
+ *
+ * Styles defined here are injected into a components' shadow DOM.
+ */

package/src/authority/airtable.js

@@ -4,11 +4,11 @@ import { resolveURL } from '../utils.js';
 
 function expandTemplate(template = '', options) {
   return template.replace(/\${([^}]+)}/g, (match, p) => {
-      let replacement;
-      if (options[p]) {
-          replacement = options[p];
-      }
-      return replacement || '';
+    let replacement;
+    if (options[p]) {
+      replacement = options[p];
+    }
+    return replacement || '';
   });
 }
 
@@ -23,7 +23,6 @@ function getTemplate(configElem, selector) {
 }
 
 export class Airtable extends Registry {
-
   constructor(configElem) {
     super(configElem);
     this.apiKey = configElem.getAttribute('api-key');
@@ -45,7 +44,7 @@ export class Airtable extends Registry {
       this.tokenize = [this.fields[0]];
     }
 
-    this.tokenizeChars = configElem.getAttribute('tokenize-regex') || "\\W";
+    this.tokenizeChars = configElem.getAttribute('tokenize-regex') || '\\W';
 
     this.infoExpr = getTemplate(configElem, '.info');
     this.detailExpr = getTemplate(configElem, '.detail');
@@ -54,14 +53,12 @@ export class Airtable extends Registry {
   }
 
   _init() {
-      window.ESGlobalBridge.requestAvailability();
-      const path = resolveURL('../lib/airtable.browser.js');
-      window.ESGlobalBridge.instance.load('airtable', path);
-      window.addEventListener(
-        'es-bridge-airtable-loaded',
-        this._initAirtable.bind(this),
-        { once: true },
-      );
+    window.ESGlobalBridge.requestAvailability();
+    const path = resolveURL('../lib/airtable.browser.js');
+    window.ESGlobalBridge.instance.load('airtable', path);
+    window.addEventListener('es-bridge-airtable-loaded', this._initAirtable.bind(this), {
+      once: true,
+    });
   }
 
   _initAirtable() {
@@ -76,7 +73,7 @@ export class Airtable extends Registry {
     const options = {
       fields: this.fields,
       // Selecting the first 3 records in Grid view:
-      maxRecords: 100
+      maxRecords: 100,
     };
     if (this.view) {
       options.view = this.view;
@@ -95,13 +92,15 @@ export class Airtable extends Registry {
           }
           records.forEach(record => {
             const data = {};
-            this.fields.forEach((field) => { data[field] = record.get(field); });
+            this.fields.forEach(field => {
+              data[field] = record.get(field);
+            });
             const result = {
               register: this._register,
               id: record.id,
               label: expandTemplate(this.labelExpr, data),
               details: expandTemplate(this.detailExpr, data),
-              provider: 'airtable'
+              provider: 'airtable',
             };
             results.push(result);
           });
@@ -133,7 +132,7 @@ export class Airtable extends Registry {
         }
         let strings = [];
         const data = {};
-        this.fields.forEach((field) => {
+        this.fields.forEach(field => {
           const value = record.get(field);
           if (value) {
             data[field] = value;
@@ -141,7 +140,7 @@ export class Airtable extends Registry {
           }
         });
         const regex = new RegExp(this.tokenizeChars);
-        this.tokenize.forEach((key) => {
+        this.tokenize.forEach(key => {
           if (data[key]) {
             strings = strings.concat(data[key].split(regex));
           }
@@ -152,7 +151,7 @@ export class Airtable extends Registry {
 
         resolve({
           id: record.id,
-          strings
+          strings,
         });
       });
     });