@digital-realty/ui-knowledgebase 0.1.0

package/README.md

@@ -0,0 +1,483 @@
+# ui-knowledgebase
+
+Knowledge Base micro-frontend for the Global Portal. Rebuilds the legacy iframe-based
+KB (Next.js + Strapi v4) as a native Lit MFE reading from Strapi 5 REST.
+
+MFE standup and shell/host integration are tracked separately. This README logs the
+component and API-integration tickets as we define them.
+
+**Component approach:** self-contained components per content type / Post `behavior`
+(mirroring v1: `kb-post-text`, `kb-post-accordion`, `kb-post-video-card`,
+`kb-post-document-card`, `kb-category-tile`, `kb-topic-tile`, …) rather than reusable
+atoms — favouring fast, easy-to-follow code. The one shared exception is `kb-rich-text`
+(KB-2), which all post components delegate to so sanitization stays centralized.
+
+## Page component maps
+
+Annotated UAT screenshots mapping every component per page (boxes named with their ticket).
+
+**Landing** (`/`)
+![Landing page component map](docs/audit-landing-page.png)
+
+**Category** (`/category/:uid`) — note the chrome tickets: back button, category sidebar nav, breadcrumb.
+![Category page component map](docs/audit-category-page.png)
+
+**Topic** (`/topic/:code`) — back button + breadcrumb, no sidebar.
+![Topic page component map](docs/audit-topic-page.png)
+
+**What's New category** — adds the year filter.
+![What's New page component map](docs/audit-whatsnew-page.png)
+
+_Details (`/details/:uid`) is just title + rich-text body in UAT — no back button or breadcrumb._
+
+## Tickets
+
+### KB-1 · KB Strapi API client
+
+_No UI — API / data layer._
+
+**Type:** Story
+
+**Summary**
+The data-access layer the MFE uses to read content from Strapi 5. Wraps `fetch`
+against the Strapi REST API, normalizes Strapi's response shape into stable view
+models, and exposes typed methods per KB view. UI components consume these methods and
+never touch raw Strapi JSON.
+
+**Background**
+Content is public-read. Strapi 5 responses are flat (no `data.attributes` wrapper),
+`documentId` replaces numeric `id` for lookups, and `status` replaces `publicationState`.
+Media URLs vary by environment (Azurite locally, Azure Blob in prod), so they resolve
+through a configurable base. Base URLs come from `window.gpConfig['ui-knowledge-base']`
+via the MFE's `config-helper.ts`, matching the other MFEs.
+
+**Scope**
+- A `StrapiClient` service reading `apiBaseUrl` and a media base URL from config; no hardcoded hosts.
+- Typed methods for the four views:
+  - `getLanding()` — index-page single type + categories + topics + featured + what's-new posts
+  - `getCategory(uid)` — category by uid plus its published posts, with sort and topic-filter params
+  - `getTopic(code)` — published posts for a topic
+  - `getPost(uid)` — single post, populating thumbnail, video, documents, topics, category
+- Normalization into KB view-model types: flatten Strapi shape, expose `documentId`, resolve media URLs to absolute.
+- Query building for `populate`, `locale`, `status=published`, pagination, and `filters`.
+- Consistent error handling: non-2xx and network failures surface as a typed error for page views to render.
+
+**Out of scope**
+- Search (separate ticket), rich-text rendering, and any write operations.
+- Auth/token handling — assumes public read; an API token is a follow-up if gating is later required.
+
+**Acceptance criteria**
+- All four methods return normalized view models; no component references `data.attributes` or raw Strapi fields.
+- Base URLs are config-driven; switching config points the client at local vs deployed Strapi with no code change.
+- Media URLs in returned models are absolute and load in both local (Azurite) and deployed environments.
+- Only published content is returned by default; `locale` is honored when passed.
+- Failures return a typed error; a smoke test covers a 404 and a network error.
+- Unit tests cover normalization and query building for each method.
+
+**Dependencies**
+- Config-helper + config keys ticket (provides `apiBaseUrl` / media base).
+- View-model types ticket.
+- Strapi public-role read access enabled.
+
+### KB-2 · Build sanitized rich-text (HTML) renderer
+
+![KB-2 rich-text renderer](docs/KB-02-rich-text.png)
+_UAT reference: the sanitized HTML body (paragraph, list, PDF link) inside an expanded What's New accordion._
+
+**Type:** Story
+
+**Summary**
+Render a post's `text` field (raw CKEditor HTML from Strapi) safely. A pure helper
+sanitizes and rewrites URLs; a thin Lit element applies it so post HTML can only be
+rendered through the sanitizer.
+
+**Background**
+The legacy frontend did **no** sanitization — it injected the HTML directly (or parsed it
+with `html-react-parser`, which only rewrote anchors/images). It got away with this because
+it ran in a separate-origin iframe. This MFE runs in the portal's own origin, so unsafe HTML
+could run with portal privileges. The `text` HTML also contains messy pasted-Word markup and
+inline `/uploads/...` links. GPv1 already wrapped rendering in a reused `RawHtml` component;
+we mirror that and add the missing sanitize step.
+
+**Scope**
+- `sanitizeRichText(html, mediaBase): string` — pure helper using DOMPurify (allowlist
+  tolerant of the legacy Word markup). Rewrite `<a href>` / `<img src>` via a DOMPurify
+  `afterSanitizeAttributes` hook: resolve relative `/uploads/...` against the media base URL,
+  leave absolute URLs as-is, add `target="_blank" rel="noopener noreferrer"` to external links.
+  (Ports the URL logic from GPv1's `renderTextAsJsx`; the old `/api/files?url=` proxy is dropped.)
+- `<kb-rich-text .value>` — thin Lit element that calls the helper and renders via `unsafeHTML`;
+  the single place `unsafeHTML` is used. Renders in **light DOM** (`createRenderRoot()` returns
+  `this`) so portal styles cascade onto the CMS content; content-specific CSS (tables, lists,
+  headings) lives as a scoped `.kb-rich-text` class in the MFE stylesheet, not `static styles`.
+  Trade-off: no style encapsulation — acceptable for CMS content; the sanitizer, not the DOM
+  boundary, is the security control.
+
+**Out of scope**
+- Video embeds and document/attachment lists (separate components).
+
+**Acceptance criteria**
+- `<script>`, event handlers, and other unsafe content are stripped; a test asserts a script payload does not execute.
+- Relative media URLs resolve to absolute against the media base and load locally (Azurite) and deployed.
+- External links open in a new tab with `rel="noopener noreferrer"`.
+- Representative legacy content (incl. the pasted-Word Terms & Conditions post) renders without breaking layout.
+
+**Dependencies**
+- KB-1 (media base URL / normalized models).
+
+### KB-3 · Build Knowledge Base landing page view
+
+![KB-3 landing view](docs/KB-03-landing-view.png)
+
+**Type:** Story
+
+**Summary**
+The landing route (`/`) of the KB MFE. Fetches the landing data and composes the page
+sections, wiring navigation into category, topic, and post-detail routes.
+
+**Background**
+Mirrors the legacy KB home: a hero (from the `IndexPage` single type) plus Categories,
+Topics, Featured Resources, and a What's New panel. This ticket is the page composition
+only — each section is its own component ticket.
+
+**Scope**
+- A Lit route view at `/` that calls `StrapiClient.getLanding()` (KB-1).
+- Compose the sections: hero + search, categories grid, topics list, featured resources, what's-new panel.
+- Wire clicks: category → `/category/:uid`, topic → `/topic/:code`, post → `/details/:uid`.
+- Render loading, empty, and error states from the client result.
+
+**Out of scope**
+- The section components themselves (hero, category card, topics list, featured card, what's-new) — separate tickets.
+- Search behaviour (separate ticket); this view only places the search input.
+
+**Acceptance criteria**
+- Landing renders all five sections from a single `getLanding()` call.
+- Category, topic, and post links navigate to the correct routes.
+- Loading, empty, and error states render; an error from the client shows the error state, not a blank page.
+
+**Dependencies**
+- KB-1 (client + `getLanding()`).
+- Content components: `kb-category-tile`, `kb-topic-tile`, featured post cards, `kb-whats-new-panel` (hero inline or `kb-hero`).
+
+### KB-4 · `kb-hero`
+
+![KB-4 hero](docs/KB-04-hero.png)
+
+**Type:** Story
+
+**Summary**
+Landing banner built from the `IndexPage` single type.
+
+**Data:** `heading`, `description`, `backgroundImage`.
+
+**Renders:** background image with heading + description; provides the slot/placement for the search input (search behaviour is a separate ticket).
+
+**Dependencies:** KB-1.
+
+### KB-5 · `kb-category-tile`
+
+![KB-5 category tile](docs/KB-05-category-tile.png)
+
+**Type:** Story
+
+**Summary**
+A single category card, repeated in the landing categories grid.
+
+**Data:** `uid`, `title`, `subtitle`, `icon` (Material icon name), `image`.
+
+**Renders:** card with icon/image, title, subtitle; click navigates to `/category/:uid`.
+
+**Dependencies:** KB-1.
+
+### KB-6 · `kb-topic-tile`
+
+![KB-6 topic tile](docs/KB-06-topic-tile.png)
+
+**Type:** Story
+
+**Summary**
+A single topic link/chip, repeated in the landing topics list.
+
+**Data:** `code`, `name`, `icon`.
+
+**Renders:** icon + name; click navigates to `/topic/:code`.
+
+**Dependencies:** KB-1.
+
+### KB-7 · `kb-featured-card`
+
+![KB-7 featured card](docs/KB-07-featured-card.png)
+
+**Type:** Story
+
+**Summary**
+A post preview card used in the landing "Featured Resources" row.
+
+**Data:** `uid`, `title`, `abstract`, `thumbnail`, `topics`.
+
+**Renders:** thumbnail, topic tag(s), title, abstract; click navigates to `/details/:uid`.
+
+**Dependencies:** KB-1.
+
+### KB-8 · `kb-whats-new-panel`
+
+![KB-8 what's-new panel](docs/KB-08-whats-new-panel.png)
+
+**Type:** Story
+
+**Summary**
+The landing "What's New" side panel.
+
+**Data:** the what's-new category (`title`, `subtitle`) + its recent posts (`title`, `dateAdded`, `uid`).
+
+**Renders:** heading + subtitle, a short list of recent posts (title/date, link to `/details/:uid`), and a "view all" link to `/category/whats-new`.
+
+**Dependencies:** KB-1.
+
+### KB-9 · `kb-post-text`
+
+![KB-9 post text](docs/KB-09-post-text.png)
+_UAT reference: the Terms, Policies & Disclaimers category (text-behavior posts)._
+
+**Type:** Story
+
+**Summary**
+Post renderer for `behavior = text` (article-style body).
+
+**Data:** `title`, `dateAdded`, `topics`, `text`.
+
+**Renders:** title, date, topic chips, and body HTML via `<kb-rich-text>`.
+
+**Dependencies:** KB-1, KB-2.
+
+### KB-10 · `kb-post-accordion`
+
+![KB-10 post accordion](docs/KB-10-post-accordion.png)
+_UAT reference: What's New category (also accordion-behavior); V2 FAQs is empty in UAT._
+
+**Type:** Story
+
+**Summary**
+Post renderer for `behavior = accordion` (used by FAQ categories).
+
+**Data:** `title`, `text`.
+
+**Renders:** an accordion item — title as the header, body HTML via `<kb-rich-text>` in the expandable panel (may use `ix-accordion`).
+
+**Dependencies:** KB-1, KB-2.
+
+### KB-11 · `kb-post-video-card`
+
+![KB-11 post video card](docs/KB-11-post-video-card.png)
+_UAT reference: the video player from the video post's detail page — UAT has no `video_card` category, so the card layout isn't shown (use Figma for that)._
+
+**Type:** Story
+
+**Summary**
+Post renderer for `behavior = video_card`.
+
+**Data:** `title`, `topics`, `thumbnail`, `video`, `duration`, `text`.
+
+**Renders:** card with video thumbnail + duration and a play action that opens the video; title, topic chips, and body HTML via `<kb-rich-text>`.
+
+**Dependencies:** KB-1, KB-2 (video player/embed is part of this component).
+
+### KB-12 · `kb-post-document-card`
+
+![KB-12 post document card](docs/KB-12-post-document-card.png)
+_UAT reference: the User Guides category (document_card-behavior posts)._
+
+**Type:** Story
+
+**Summary**
+Post renderer for `behavior = document_card`.
+
+**Data:** `title`, `topics`, `documents[]`, `text`.
+
+**Renders:** card with title, topic chips, body HTML via `<kb-rich-text>`, and a list of downloadable document links from `documents[]`.
+
+**Dependencies:** KB-1, KB-2.
+
+### KB-13 · Build category listing page view
+
+![KB-13 category view](docs/KB-13-category-view.png)
+![KB-13 sort + topic filter controls](docs/KB-13b-sort-filter-controls.png)
+_Second image: the flag-driven sort + topic-filter controls (shown only when `showSortBy` / `showFilterByTopic` are set)._
+
+**Type:** Story
+
+**Summary**
+The category route (`/category/:uid`). Fetches a category and its posts, and renders the
+posts using the category's `behavior`.
+
+**Background**
+Mirrors the legacy category page. A category's `behavior` (`text | accordion |
+video_card | document_card`) decides which post component renders its posts, and its
+`showSortBy` / `showFilterByTopic` flags decide whether the sort and topic-filter
+controls appear.
+
+**Scope**
+- A Lit route view at `/category/:uid` calling `StrapiClient.getCategory(uid)` (KB-1).
+- Header from the category (title, subtitle, icon/image).
+- Render the posts by selecting the post component from the category `behavior`
+  (KB-9 `text`, KB-10 `accordion`, KB-11 `video_card`, KB-12 `document_card`).
+- Show inline sort and filter-by-topic controls only when `showSortBy` / `showFilterByTopic` are set.
+- Post click → `/details/:uid`; loading, empty, and error states.
+
+**Out of scope**
+- The post components themselves (KB-9–12); search.
+
+**Acceptance criteria**
+- Posts render with the component matching the category `behavior`.
+- Sort / topic-filter controls appear only when their flags are set, and filter/sort the list.
+- Loading, empty, and error states render.
+
+**Dependencies:** KB-1, KB-9, KB-10, KB-11, KB-12, KB-17 (back button), KB-18 (sidebar nav), KB-19 (breadcrumb); KB-20 (year filter) on the What's New category.
+
+### KB-14 · Build topic listing page view
+
+![KB-14 topic view](docs/KB-14-topic-view.png)
+
+**Type:** Story
+
+**Summary**
+The topic route (`/topic/:code`). Fetches the posts for a topic and renders each by its
+own `behavior`.
+
+**Background**
+Mirrors the legacy topic page. Unlike a category, a topic's posts span categories, so
+each post renders according to its own `behavior` field.
+
+**Scope**
+- A Lit route view at `/topic/:code` calling `StrapiClient.getTopic(code)` (KB-1).
+- Header showing the topic (icon + name).
+- Render each post by selecting the post component from that post's `behavior` (KB-9–12).
+- Post click → `/details/:uid`; loading, empty, and error states.
+
+**Out of scope**
+- The post components themselves (KB-9–12); search.
+
+**Acceptance criteria**
+- Each post renders with the component matching its own `behavior`.
+- Loading, empty, and error states render.
+
+**Dependencies:** KB-1, KB-9, KB-10, KB-11, KB-12, KB-17 (back button), KB-19 (breadcrumb). No sidebar on topic pages.
+
+### KB-15 · Build post details page view
+
+![KB-15 details view](docs/KB-15-details-view.png)
+
+**Type:** Story
+
+**Summary**
+The post detail route (`/details/:uid`). Renders a single post in full.
+
+**Background**
+Mirrors the legacy details page — the full post: title, topics, date, body, and any
+video or document attachments. Keep the `/details/:uid` path; deep links and the
+launchpad widget depend on it.
+
+**Scope**
+- A Lit route view at `/details/:uid` calling `StrapiClient.getPost(uid)` (KB-1).
+- Render: title, topic chips, `dateAdded`, body HTML via `<kb-rich-text>` (KB-2),
+  the `video` if present, and the `documents[]` as downloadable links.
+- Loading, not-found (bad uid), and error states.
+
+**Out of scope**
+- Search; related-posts / navigation beyond back.
+
+**Acceptance criteria**
+- A post renders its title, body, and any video/documents.
+- Body HTML is sanitized via `<kb-rich-text>` and media links resolve.
+- An unknown `uid` shows a not-found state, not a blank page.
+
+**Dependencies:** KB-1, KB-2.
+
+### KB-16 · Knowledge Base search
+
+![KB-16 search](docs/KB-16-search.png)
+
+**Type:** Story
+
+**Summary**
+Search across KB posts from the hero search input, with a results list that links to posts.
+
+**Background**
+The legacy KB hero has a search box. Content is small, so a simple substring match is
+enough — no ranking engine. Runs against Strapi REST.
+
+**Scope**
+- Add `StrapiClient.search(query)` (KB-1) using Strapi filters (`$containsi` on `title`,
+  `abstract`, `text`), published-only and locale-aware, returning normalized post previews.
+- Wire the hero search input (KB-4): debounce input, call `search`, and show results.
+- Render results as a simple list (title, abstract, category/topic); click → `/details/:uid`.
+- Handle empty query, no-results, and error states.
+
+**Out of scope**
+- Ranking / relevance scoring, faceting, and search analytics.
+
+**Acceptance criteria**
+- Typing a query returns matching published posts; matches are case-insensitive across title/abstract/text.
+- Selecting a result navigates to `/details/:uid`.
+- Empty query clears results; no-results and error states render.
+
+**Dependencies:** KB-1, KB-4.
+
+_Note: the search input also appears on the category and topic pages (same component, different placement), not only the hero._
+
+### KB-17 · `kb-back-button`
+
+**Type:** Story
+
+![KB-17 back button](docs/KB-17-back-button.png)
+
+**Summary**
+The "← BACK" control shown top-left on the category, topic, and any nested page.
+
+**Renders:** a back arrow + "BACK" label; navigates to the previous route (history back, falling back to the KB landing).
+
+**Dependencies:** none (pure navigation).
+
+### KB-18 · `kb-category-nav`
+
+**Type:** Story
+
+![KB-18 category sidebar nav](docs/KB-18-category-nav.png)
+
+**Summary**
+The left-hand sidebar listing all categories on a category page, with the current one highlighted.
+
+**Data:** all categories (`uid`, `title`) — from KB-1.
+
+**Renders:** a vertical list of category links; current category highlighted; each links to `/category/:uid`. (Category pages only — topic/landing/details don't show it.)
+
+**Dependencies:** KB-1.
+
+### KB-19 · `kb-breadcrumb`
+
+**Type:** Story
+
+![KB-19 breadcrumb](docs/KB-19-breadcrumb.png)
+
+**Summary**
+The breadcrumb trail (e.g. `Knowledge Base › User Guides`) on category and topic pages.
+
+**Data:** the current page's label + parent (Knowledge Base root).
+
+**Renders:** links back to `/` (Knowledge Base) and shows the current page; last crumb is non-clickable.
+
+**Dependencies:** none (labels passed in by the page view).
+
+### KB-20 · `kb-whats-new-year-filter`
+
+**Type:** Story
+
+![KB-20 What's New year filter](docs/KB-20-year-filter.png)
+
+**Summary**
+The year pills (e.g. `2025` / `2026`) on the What's New category that filter release-note posts by year.
+
+**Data:** the set of years present in the category's posts (`dateAdded`).
+
+**Renders:** a row of selectable year pills; selecting one filters the accordion list to that year. (What's New category only.)
+
+**Dependencies:** KB-1, KB-13.

package/dist/ui-knowledgebase.js

@@ -0,0 +1,39 @@
+import{LitElement as e,css as t,html as n,nothing as r}from"lit";import{customElement as i,property as a,state as o}from"lit/decorators.js";import{Router as s}from"@vaadin/router";var c=null;function l(e,t,n){c=new s(e,{baseUrl:t}),c.setRoutes(n)}function u(){return c}function d(){c?.unsubscribe(),c?.removeRoutes(),c=null}function f(e,t,n,r){var i=arguments.length,a=i<3?t:r===null?r=Object.getOwnPropertyDescriptor(t,n):r,o;if(typeof Reflect==`object`&&typeof Reflect.decorate==`function`)a=Reflect.decorate(e,t,n,r);else for(var s=e.length-1;s>=0;s--)(o=e[s])&&(a=(i<3?o(a):i>3?o(t,n,a):o(t,n))||a);return i>3&&a&&Object.defineProperty(t,n,a),a}var p=class extends e{static{this.styles=t`
+    :host {
+      display: block;
+      padding: 1rem;
+    }
+  `}render(){return n`
+      <h1>Knowledge Base</h1>
+      <nav>
+        <ul>
+          <li><a href="/knowledge-base/category/demo">Category: demo</a></li>
+          <li><a href="/knowledge-base/topic/demo">Topic: demo</a></li>
+          <li><a href="/knowledge-base/details/demo">Details: demo</a></li>
+        </ul>
+      </nav>
+    `}};p=f([i(`kb-landing-view`)],p);var m=class extends e{constructor(...e){super(...e),this.uid=``}static{this.styles=t`
+    :host {
+      display: block;
+      padding: 1rem;
+    }
+  `}onAfterEnter(e){this.uid=String(e.params.uid??``)}render(){return n`
+      <a href="/knowledge-base">&larr; Knowledge Base</a>
+      <h1>Category: ${this.uid}</h1>
+    `}};f([o()],m.prototype,`uid`,void 0),m=f([i(`kb-category-view`)],m);var h=class extends e{constructor(...e){super(...e),this.code=``}static{this.styles=t`
+    :host {
+      display: block;
+      padding: 1rem;
+    }
+  `}onAfterEnter(e){this.code=String(e.params.code??``)}render(){return n`
+      <a href="/knowledge-base">&larr; Knowledge Base</a>
+      <h1>Topic: ${this.code}</h1>
+    `}};f([o()],h.prototype,`code`,void 0),h=f([i(`kb-topic-view`)],h);var g=class extends e{constructor(...e){super(...e),this.uid=``}static{this.styles=t`
+    :host {
+      display: block;
+      padding: 1rem;
+    }
+  `}onAfterEnter(e){this.uid=String(e.params.uid??``)}render(){return n`
+      <a href="/knowledge-base">&larr; Knowledge Base</a>
+      <h1>Details: ${this.uid}</h1>
+    `}};f([o()],g.prototype,`uid`,void 0),g=f([i(`kb-details-view`)],g);var _=`/knowledge-base`,v=e=>e===`/knowledge-base`||e.startsWith(`/knowledge-base/`),y={Landing:`kb-landing`,Category:`kb-category`,Topic:`kb-topic`,Details:`kb-details`},b=[{path:_,children:[{name:y.Landing,path:`/`,component:`kb-landing-view`},{name:y.Category,path:`/category/:uid`,component:`kb-category-view`},{name:y.Topic,path:`/topic/:code`,component:`kb-topic-view`},{name:y.Details,path:`/details/:uid`,component:`kb-details-view`}]},{path:`(.*)`,component:`no-elem`}],x=class extends e{constructor(...e){super(...e),this.baseUrl=`/`,this.active=!1,this.outlet=document.createElement(`main`),this.onLocationChanged=e=>{let{router:t,location:n}=e.detail;t===u()&&(this.active=v(n.pathname))}}connectedCallback(){super.connectedCallback(),window.addEventListener(`vaadin-router-location-changed`,this.onLocationChanged),l(this.outlet,this.baseUrl,b),this.dispatchEvent(new CustomEvent(`mfe-loaded`,{detail:{routes:b}}))}disconnectedCallback(){super.disconnectedCallback(),window.removeEventListener(`vaadin-router-location-changed`,this.onLocationChanged),d(),this.active=!1}render(){return this.active?n`${this.outlet}`:r}};f([a({type:String})],x.prototype,`baseUrl`,void 0),f([o()],x.prototype,`active`,void 0),x=f([i(`ui-knowledgebase`)],x);export{x as UiKnowledgebase};

package/package.json

@@ -0,0 +1,31 @@
+{
+  "name": "@digital-realty/ui-knowledgebase",
+  "version": "0.1.0",
+  "type": "module",
+  "packageManager": "pnpm@11.7.0",
+  "publishConfig": {
+    "access": "public"
+  },
+  "files": [
+    "dist"
+  ],
+  "exports": {
+    "./ui-knowledgebase.js": "./dist/ui-knowledgebase.js"
+  },
+  "scripts": {
+    "dev": "vite",
+    "build": "tsc --noEmit && vite build",
+    "build:workspace": "pnpm run build",
+    "preview": "vite preview",
+    "clean": "rimraf node_modules dist"
+  },
+  "dependencies": {
+    "@vaadin/router": "^1.7.5",
+    "lit": "^3.1.4"
+  },
+  "devDependencies": {
+    "rimraf": "^6.0.1",
+    "typescript": "^5.5.3",
+    "vite": "^8.1.0"
+  }
+}