@gitkraken/core-gitlens 0.7.1 → 0.8.0

package/docs/kepler-read-api-parity.md

@@ -182,34 +182,81 @@ which excludes unassigned issues. A provider that declares no filtered search ke
 See the note in `reads/broaden.ts` and
 [`integrations.md` §9](./integrations.md#9-per-provider-behavior-worth-designing-around).
 
-**Batch issue resolution (#5802).** `getIssuesBatch` resolves N `(owner, repo, number)` coordinates in one
-request, for the identity question a search cannot answer: "which issue does this branch name reference".
-It aliases the point read rather than a search, so there is no result ceiling and no ordering — and an
-absent slot is a PROVEN absence rather than "not found within a page budget", which is what lets a consumer
-CACHE a miss. A target whose chunk failed is not returned at all, so the two stay distinguishable; caching a
-failure as an absence is the bug that distinction prevents. GitHub/GHE only, matching `countIssues`.
-
-**Tracker issue resolution by key (#5810).** `getTrackerIssue` is the same identity read for an issue TRACKER,
-which `getIssuesBatch` cannot serve: its target is `(owner, repo, number)`, and a tracker issue is addressed by
-`(resourceId, ABC-123)` — no owner, no repo, and an identifier that is not a number. It answers in one request
-where the only published tracker surface (`listIssueTrackerIssuesPage`) needs a scoped page-walk that cannot
-prove absence without draining the whole scope. Same absence/failure contract as the batch read, and the same
-reason it matters: a tracker miss is the common outcome and was never cacheable.
-
-`resourceId` is required and trusted, so the read performs no resource discovery. Jira also requires
-`resourceUrl`, obtained alongside the resource ID, because the issue response's `self` is an API endpoint rather
-than a browser link; supplying both retains the one-request contract. Linear needs only the resource ID. Jira and
-Linear only; Trello refuses because its single-issue read can fall back to a capped board scan for a numeric
-identifier, where a "not found" result cannot be distinguished from a card beyond the cap.
-
-**Jira Data Center point reads (#5872).** The same read serves a self-hosted Jira instance once it carries the host:
-`getTrackerIssue` takes the `domain` its paged siblings already took, and `resourceId` is the host itself (the
-instance's single resource; one naming another host than the read resolves to is refused). It does NOT fall back to the primary connection the way the paged reads do — a
-self-managed tracker requires a `domain` or a `connectionId` with a configured host and is refused otherwise —
-because its proven absence is cacheable and two self-hosted instances routinely issue the same keys, so an answer
-from whichever host is primary would be cached under a key naming a different instance. The branch-association
-resolver (`getIssueFromGitConfigEntityIdentifier`) follows the same rule from the other side: its resolver receives
-the identifier's `domain`, and a Jira Data Center identifier without one is dropped rather than resolved.
+**Batch issue resolution (#5802, #5810).** `getIssuesBatch` resolves N issues by identity in one call, for the
+identity question a search cannot answer: "which issue does this branch name reference". It uses the point read
+rather than a search, so there is no result ceiling and no ordering — and an absent slot is a PROVEN absence
+rather than "not found within a page budget", which is what lets a consumer CACHE a miss. A target that failed —
+its whole request, or just that target, e.g. in an org enforcing SAML SSO the token isn't authorized for — is not
+returned at all, so the two stay distinguishable; caching a failure as an absence is the bug that distinction
+prevents.
+
+A target takes the form its provider addresses an issue by. GitHub/GHE take `(owner, repo, number)` coordinates,
+aliased up to 25 per request. A tracker issue is addressed by `(resourceId, ABC-123)` — no owner, no repo, and an
+identifier that is not a number — so Jira (Cloud and Data Center) and Linear take
+`{ key, resourceId, resourceUrl?, identifier }` targets, each answered by the single-issue read the tracker already
+implements. That replaces a scoped page-walk over `listIssueTrackerIssuesPage`, which cannot prove absence without
+draining the whole scope, where a miss is the common outcome. A key asked of several resources is one call with one
+target per resource. `resourceId` is trusted, so the read performs no resource discovery; Jira Cloud also requires
+`resourceUrl`, because the issue response's `self` is an API endpoint rather than a browser link. Trello refuses:
+its single-issue read can fall back to a capped board scan for a numeric identifier, where a "not found" cannot be
+told from a card beyond the cap. Bitbucket and Bitbucket DC, which have no issues, refuse too.
+
+GitLab and Azure DevOps take the same coordinates as GitHub, plus `project` on Azure DevOps, whose work items belong to
+the project rather than to a repository, so `repo` is ignored there. They cost one request per target and replace a
+scoped page-walk over `listIssuesPage`, which could not prove absence either. Neither host's existing single-issue
+read could, so each has a strict one. A GitLab miss costs a second request, because provider-apis reports a reply
+carrying only GraphQL errors the same way as a missing issue. An Azure DevOps miss is trusted only on Azure's own
+not-found body: `WorkItemUnauthorizedAccessException` (TF401232, "does not exist, or you do not have permissions to
+read it", so absent means not visible to this connection) or `ProjectDoesNotExistWithNameException`. An HTML 404, a
+410 or any other failure fails the target. Rows match the repository-scoped `listIssuesPage` rows, except that an
+Azure DevOps row has no `project`.
+
+A self-hosted Jira (Data Center, #5872) is served by the same tracker targets once the call carries the host:
+`getIssuesBatch` takes the `domain` its paged siblings take, and a target's `resourceId` is the host itself (the
+instance's single resource; a call with any target naming another host than the read resolves to is refused whole).
+It does NOT fall back to the primary connection the way the paged reads do — a self-managed tracker requires a
+`domain` or a `connectionId` with a configured host and the call is refused otherwise — because its proven absence
+is cacheable and two self-hosted instances routinely issue the same keys, so an answer from whichever host is
+primary would be cached under a key naming a different instance. The branch-association resolver
+(`getIssueFromGitConfigEntityIdentifier`) follows the same rule from the other side: its resolver receives the
+identifier's `domain`, and a Jira Data Center identifier without one is dropped rather than resolved.
+
+**Batch pull request resolution.** `getPullRequestsBatch` is the identity read for pull requests: N
+`(owner, repo, number)` coordinates, plus `project` on Azure DevOps, in any state. Before it the facade had only
+list, search, count and sweep reads for pull requests, so a consumer found one by scanning its repository's most
+recently updated pull requests per state and matching the URL — and an older merged pull request could be neither
+found nor proven gone. Same absence/failure contract as `getIssuesBatch`. It serves every git host, Bitbucket and
+Bitbucket DC included: GitHub/GHE alias up to 25 point reads into one document, while GitLab, Bitbucket, Bitbucket
+DC and Azure DevOps have no batch form and cost one request per target. A GitLab miss costs a second request, because
+provider-apis' GitLab read reports a reply that carries only GraphQL errors the same way as a missing merge
+request, so its `null` alone does not prove absence; an Azure DevOps miss is trusted only when Azure's own error
+body names the pull request, repository or project as not found, not on any other 404 or a 410. Rows take the
+list reads' conversion on every host but Bitbucket Cloud, which has no single pull request read in provider-apis
+and so answers from GitLens' own REST read instead, missing `commentsCount`, `isDraft` and the clone URLs. On
+GitLab, a miss the confirming read then contradicts fails the target rather than answering with the confirming
+read's own, differently-identified row. The read is uncached and does not go through
+`IntegrationCacheProvider.getPullRequest`, whose key carries no connection, so the consumer's cache is the only
+one holding the answer.
+
+**Pull requests by branch.** `getPullRequestsForBranches` answers "which pull requests have this branch as their
+head, in this repository" with no relationship to the user. Before it, Kepler correlated a local branch by matching
+the account-wide sweep, which holds only pull requests the user authored, is assigned or reviews — so a teammate's
+pull request from the user's branch never correlated — and a cold card paid for that whole sweep before showing
+anything. It matches on the head branch name in every state, so a merged pull request whose branch was deleted is
+still found, and on the head repository, the base one or the `headOwner` fork, so a same-named branch in another
+fork never correlates; a `headOwner` equal to the owner means the base repository, so Kepler can pass the owner of
+the remote the branch was pushed to. Up to 10 per branch; an empty list without `truncated` is a proven none a
+consumer can cache, and a failed target is dropped with `fetchFailed`. GitHub/GHE answer up to 25 branches per
+request, and every other host costs one request per branch. GitLab and Azure DevOps resolve each match (typically
+0–1 per branch) through `getPullRequestsBatch`'s own read, so a pull request's `url`, and so its identity, is the
+same whichever read found it. Bitbucket DC and Azure DevOps serve base-repository branches only and refuse a
+`headOwner` naming another owner.
+
+**Current account resolution.** `getCurrentAccount` answers who a git host connection is signed in as, on
+demand. Before it, Kepler learned the viewer's account only when its `IntegrationManagerCacheProvider`
+`getCurrentAccount` hook fired during some other read, so "is this pull request mine" could stay unanswered until
+something else resolved the account. The read goes through that same hook, so there is still one cache. `account`
+is never absent without a warning. Jira, Linear and Trello refuse: they have only a per-resource account.
 
 **Kepler-side follow-up:** `ProviderScopeFilter` carries a single `repo?: string` today and needs the criteria
 set; the `provider-data` adapter then routes "All visible" to `searchIssuesPage` + `countIssues`.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@gitkraken/core-gitlens",
   "description": "GitLens core — shared Git / AI / GitHub primitives for internal GitKraken consumption",
-  "version": "0.7.1",
+  "version": "0.8.0",
   "license": "SEE LICENSE IN LICENSE",
   "author": {
     "name": "GitKraken",

package/dist/plus/integrations/reads/trackerIssue.d.ts

@@ -1,33 +0,0 @@
-import { IssueShape } from "../../../git/models/issue.js";
-import { IntegrationIds } from "../constants.js";
-import { ProviderResult } from "../results.js";
-import { ProviderReadContext } from "./context.js";
-//#region ../plus/integrations/src/reads/trackerIssue.d.ts
-export interface TrackerIssueResult {
-  key: string;
-  /**
-   * The resolved issue, or `undefined` when it provably does not exist or is not visible to this connection.
-   * A failed read returns no item and sets `fetchFailed`.
-   */
-  issue?: IssueShape;
-}
-/**
- * `domain` selects the host of a self-managed tracker (Jira Data Center), as it does for
- * `listIssueTrackerIssuesPage`, and is ignored for the cloud trackers, which have a single canonical host.
- *
- * Unlike its siblings, this read never falls back to the primary connection for a self-managed tracker: it
- * requires a `domain` or a `connectionId` with a configured host and refuses otherwise. Two self-hosted
- * instances routinely issue the same project and issue keys, and this read's `issue: undefined` is a proven
- * absence a caller may cache — an answer from whichever host happens to be primary would be cached under a key
- * that names a different instance (#5872).
- */
-export declare function getTrackerIssue(ctx: ProviderReadContext, options: {
-  providerId: IntegrationIds;
-  resourceId: string;
-  resourceUrl?: string;
-  key: string;
-  connectionId?: string;
-  domain?: string;
-}): Promise<ProviderResult<TrackerIssueResult>>;
-//#endregion
-//# sourceMappingURL=trackerIssue.d.ts.map

package/dist/plus/integrations/reads/trackerIssue.js

@@ -1,60 +0,0 @@
-import "../constants.js";
-import { areDomainsOnSameHost, hostFromDomain } from "../utils/domain.utils.js";
-import { isIssuesHostIntegrationId, isIssuesSelfManagedHostIntegrationId } from "../utils/integration.utils.js";
-import { issueTrackerOnlySurfaceWarning, otherWarning } from "./warnings.js";
-import { runCaptured } from "./drains.js";
-import { isIssuesIntegration } from "../models/issuesIntegration.js";
-//#region ../plus/integrations/src/reads/trackerIssue.ts
-/**
-* `domain` selects the host of a self-managed tracker (Jira Data Center), as it does for
-* `listIssueTrackerIssuesPage`, and is ignored for the cloud trackers, which have a single canonical host.
-*
-* Unlike its siblings, this read never falls back to the primary connection for a self-managed tracker: it
-* requires a `domain` or a `connectionId` with a configured host and refuses otherwise. Two self-hosted
-* instances routinely issue the same project and issue keys, and this read's `issue: undefined` is a proven
-* absence a caller may cache — an answer from whichever host happens to be primary would be cached under a key
-* that names a different instance (#5872).
-*/
-async function getTrackerIssue(ctx, options) {
-	const refused = (warning) => ({
-		items: [],
-		warnings: [warning],
-		fetchFailed: true
-	});
-	const surface = "Issue resolution by key";
-	if (!isIssuesHostIntegrationId(options.providerId)) return refused(issueTrackerOnlySurfaceWarning(options.providerId, options.connectionId, surface));
-	if (options.resourceId.trim().length === 0) return refused(otherWarning(options.providerId, void 0, options.connectionId, `${surface} requires a resource id.`));
-	if (options.key.trim().length === 0) return refused(otherWarning(options.providerId, void 0, options.connectionId, `${surface} requires an issue key.`));
-	const resourceUrl = options.resourceUrl?.trim() || void 0;
-	if (options.providerId === "jira" && resourceUrl == null) return refused(otherWarning(options.providerId, void 0, options.connectionId, `${surface} requires the Jira resource URL so the result contains a browser link without resource discovery.`));
-	if (isIssuesSelfManagedHostIntegrationId(options.providerId) && (options.domain != null ? hostFromDomain(options.domain) == null : options.connectionId == null || !ctx.getConfigured(options.providerId).some((c) => c.id === options.connectionId && hostFromDomain(c.domain) != null))) return refused(otherWarning(options.providerId, void 0, options.connectionId, `${surface} requires a domain or a configured connection id for '${options.providerId}': every configured host can hold a different issue under the same key, so the read does not answer from the primary connection.`));
-	const integration = await ctx.getIntegrationForRead(options.providerId, options.connectionId, options.domain);
-	if (integration == null) {
-		const early = ctx.earlyReturnConnectionWarnings(options.providerId, options.connectionId, options.domain);
-		return {
-			items: [],
-			warnings: early.warnings,
-			fetchFailed: early.fetchFailed || void 0
-		};
-	}
-	if (!isIssuesIntegration(integration)) return refused(issueTrackerOnlySurfaceWarning(options.providerId, options.connectionId, surface));
-	if (!integration.supportsIssueLookupByResourceId) return refused(otherWarning(options.providerId, void 0, options.connectionId, `${surface} is not supported by '${options.providerId}'; its single-issue read cannot prove an absence, so a miss would not be safe to cache.`));
-	if (isIssuesSelfManagedHostIntegrationId(options.providerId) && !areDomainsOnSameHost(options.resourceId, integration.domain)) return refused(otherWarning(options.providerId, void 0, options.connectionId, `${surface} requires the resource id of '${options.providerId}' to name the host the read resolved to.`));
-	const domain = ctx.domainForRead(integration, options.providerId, options.connectionId, options.domain);
-	const issue = await runCaptured(options.providerId, domain, options.connectionId, () => integration.getIssueByResourceIdResult(options.resourceId, options.key, {
-		connectionId: options.connectionId,
-		resourceUrl
-	}), { warnOnMissingSession: true });
-	if (issue.warning != null) return refused(issue.warning);
-	return {
-		items: [{
-			key: options.key,
-			...issue.value != null ? { issue: issue.value } : {}
-		}],
-		warnings: []
-	};
-}
-//#endregion
-export { getTrackerIssue };
-
-//# sourceMappingURL=trackerIssue.js.map

package/dist/plus/integrations/reads/trackerIssue.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"trackerIssue.js","names":[],"sources":["../../../../../plus/integrations/src/reads/trackerIssue.ts"],"sourcesContent":["import type { IssueShape } from '@gitlens/git/models/issue.js';\nimport type { IntegrationIds } from '../constants.js';\nimport { IssuesCloudHostIntegrationId } from '../constants.js';\nimport { isIssuesIntegration } from '../models/issuesIntegration.js';\nimport type { ProviderResult, ProviderWarning } from '../results.js';\nimport { areDomainsOnSameHost, hostFromDomain } from '../utils/domain.utils.js';\nimport { isIssuesHostIntegrationId, isIssuesSelfManagedHostIntegrationId } from '../utils/integration.utils.js';\nimport type { ProviderReadContext } from './context.js';\nimport { runCaptured } from './drains.js';\nimport { issueTrackerOnlySurfaceWarning, otherWarning } from './warnings.js';\n\nexport interface TrackerIssueResult {\n\tkey: string;\n\t/**\n\t * The resolved issue, or `undefined` when it provably does not exist or is not visible to this connection.\n\t * A failed read returns no item and sets `fetchFailed`.\n\t */\n\tissue?: IssueShape;\n}\n\n/**\n * `domain` selects the host of a self-managed tracker (Jira Data Center), as it does for\n * `listIssueTrackerIssuesPage`, and is ignored for the cloud trackers, which have a single canonical host.\n *\n * Unlike its siblings, this read never falls back to the primary connection for a self-managed tracker: it\n * requires a `domain` or a `connectionId` with a configured host and refuses otherwise. Two self-hosted\n * instances routinely issue the same project and issue keys, and this read's `issue: undefined` is a proven\n * absence a caller may cache — an answer from whichever host happens to be primary would be cached under a key\n * that names a different instance (#5872).\n */\nexport async function getTrackerIssue(\n\tctx: ProviderReadContext,\n\toptions: {\n\t\tproviderId: IntegrationIds;\n\t\tresourceId: string;\n\t\tresourceUrl?: string;\n\t\tkey: string;\n\t\tconnectionId?: string;\n\t\tdomain?: string;\n\t},\n): Promise<ProviderResult<TrackerIssueResult>> {\n\tconst refused = (warning: ProviderWarning): ProviderResult<TrackerIssueResult> => ({\n\t\titems: [],\n\t\twarnings: [warning],\n\t\tfetchFailed: true,\n\t});\n\tconst surface = 'Issue resolution by key';\n\n\tif (!isIssuesHostIntegrationId(options.providerId)) {\n\t\treturn refused(issueTrackerOnlySurfaceWarning(options.providerId, options.connectionId, surface));\n\t}\n\n\tif (options.resourceId.trim().length === 0) {\n\t\treturn refused(\n\t\t\totherWarning(options.providerId, undefined, options.connectionId, `${surface} requires a resource id.`),\n\t\t);\n\t}\n\n\tif (options.key.trim().length === 0) {\n\t\treturn refused(\n\t\t\totherWarning(options.providerId, undefined, options.connectionId, `${surface} requires an issue key.`),\n\t\t);\n\t}\n\n\tconst resourceUrl = options.resourceUrl?.trim() || undefined;\n\tif (options.providerId === IssuesCloudHostIntegrationId.Jira && resourceUrl == null) {\n\t\treturn refused(\n\t\t\totherWarning(\n\t\t\t\toptions.providerId,\n\t\t\t\tundefined,\n\t\t\t\toptions.connectionId,\n\t\t\t\t`${surface} requires the Jira resource URL so the result contains a browser link without resource discovery.`,\n\t\t\t),\n\t\t);\n\t}\n\n\t// A `domain` only selects a host when it parses to one, and a `connectionId` only when it names a configured\n\t// connection that has one; anything else would resolve the primary host instead, which is the fallback this\n\t// read refuses.\n\tif (\n\t\tisIssuesSelfManagedHostIntegrationId(options.providerId) &&\n\t\t(options.domain != null\n\t\t\t? hostFromDomain(options.domain) == null\n\t\t\t: options.connectionId == null ||\n\t\t\t\t!ctx\n\t\t\t\t\t.getConfigured(options.providerId)\n\t\t\t\t\t.some(c => c.id === options.connectionId && hostFromDomain(c.domain) != null))\n\t) {\n\t\treturn refused(\n\t\t\totherWarning(\n\t\t\t\toptions.providerId,\n\t\t\t\tundefined,\n\t\t\t\toptions.connectionId,\n\t\t\t\t`${surface} requires a domain or a configured connection id for '${options.providerId}': every configured host can hold a different issue under the same key, so the read does not answer from the primary connection.`,\n\t\t\t),\n\t\t);\n\t}\n\n\tconst integration = await ctx.getIntegrationForRead(options.providerId, options.connectionId, options.domain);\n\tif (integration == null) {\n\t\t// A supplied connectionId or domain that no longer resolves is a broken target, not an empty account.\n\t\tconst early = ctx.earlyReturnConnectionWarnings(options.providerId, options.connectionId, options.domain);\n\t\treturn { items: [], warnings: early.warnings, fetchFailed: early.fetchFailed || undefined };\n\t}\n\tif (!isIssuesIntegration(integration)) {\n\t\treturn refused(issueTrackerOnlySurfaceWarning(options.providerId, options.connectionId, surface));\n\t}\n\tif (!integration.supportsIssueLookupByResourceId) {\n\t\treturn refused(\n\t\t\totherWarning(\n\t\t\t\toptions.providerId,\n\t\t\t\tundefined,\n\t\t\t\toptions.connectionId,\n\t\t\t\t`${surface} is not supported by '${options.providerId}'; its single-issue read cannot prove an absence, so a miss would not be safe to cache.`,\n\t\t\t),\n\t\t);\n\t}\n\n\t// A self-managed tracker's single resource is its host, and the read is keyed (and cached) by `resourceId`\n\t// while it is addressed to the host `domain`/`connectionId` resolved. When they disagree, host B's answer —\n\t// including a cacheable absence — would be stored under host A's key.\n\tif (\n\t\tisIssuesSelfManagedHostIntegrationId(options.providerId) &&\n\t\t!areDomainsOnSameHost(options.resourceId, integration.domain)\n\t) {\n\t\treturn refused(\n\t\t\totherWarning(\n\t\t\t\toptions.providerId,\n\t\t\t\tundefined,\n\t\t\t\toptions.connectionId,\n\t\t\t\t`${surface} requires the resource id of '${options.providerId}' to name the host the read resolved to.`,\n\t\t\t),\n\t\t);\n\t}\n\n\tconst domain = ctx.domainForRead(integration, options.providerId, options.connectionId, options.domain);\n\tconst issue = await runCaptured(\n\t\toptions.providerId,\n\t\tdomain,\n\t\toptions.connectionId,\n\t\t() =>\n\t\t\tintegration.getIssueByResourceIdResult(options.resourceId, options.key, {\n\t\t\t\tconnectionId: options.connectionId,\n\t\t\t\tresourceUrl: resourceUrl,\n\t\t\t}),\n\t\t{ warnOnMissingSession: true },\n\t);\n\tif (issue.warning != null) {\n\t\treturn refused(issue.warning);\n\t}\n\n\treturn {\n\t\titems: [{ key: options.key, ...(issue.value != null ? { issue: issue.value } : {}) }],\n\t\twarnings: [],\n\t};\n}\n"],"mappings":";;;;;;;;;;;;;;;;;AA8BA,eAAsB,gBACrB,KACA,SAQ8C;CAC9C,MAAM,WAAW,aAAkE;EAClF,OAAO,CAAC;EACR,UAAU,CAAC,OAAO;EAClB,aAAa;CACd;CACA,MAAM,UAAU;CAEhB,IAAI,CAAC,0BAA0B,QAAQ,UAAU,GAChD,OAAO,QAAQ,+BAA+B,QAAQ,YAAY,QAAQ,cAAc,OAAO,CAAC;CAGjG,IAAI,QAAQ,WAAW,KAAK,CAAC,CAAC,WAAW,GACxC,OAAO,QACN,aAAa,QAAQ,YAAY,KAAA,GAAW,QAAQ,cAAc,GAAG,QAAQ,yBAAyB,CACvG;CAGD,IAAI,QAAQ,IAAI,KAAK,CAAC,CAAC,WAAW,GACjC,OAAO,QACN,aAAa,QAAQ,YAAY,KAAA,GAAW,QAAQ,cAAc,GAAG,QAAQ,wBAAwB,CACtG;CAGD,MAAM,cAAc,QAAQ,aAAa,KAAK,KAAK,KAAA;CACnD,IAAI,QAAQ,eAAA,UAAoD,eAAe,MAC9E,OAAO,QACN,aACC,QAAQ,YACR,KAAA,GACA,QAAQ,cACR,GAAG,QAAQ,kGACZ,CACD;CAMD,IACC,qCAAqC,QAAQ,UAAU,MACtD,QAAQ,UAAU,OAChB,eAAe,QAAQ,MAAM,KAAK,OAClC,QAAQ,gBAAgB,QACzB,CAAC,IACC,cAAc,QAAQ,UAAU,CAAC,CACjC,MAAK,MAAK,EAAE,OAAO,QAAQ,gBAAgB,eAAe,EAAE,MAAM,KAAK,IAAI,IAE/E,OAAO,QACN,aACC,QAAQ,YACR,KAAA,GACA,QAAQ,cACR,GAAG,QAAQ,wDAAwD,QAAQ,WAAW,iIACvF,CACD;CAGD,MAAM,cAAc,MAAM,IAAI,sBAAsB,QAAQ,YAAY,QAAQ,cAAc,QAAQ,MAAM;CAC5G,IAAI,eAAe,MAAM;EAExB,MAAM,QAAQ,IAAI,8BAA8B,QAAQ,YAAY,QAAQ,cAAc,QAAQ,MAAM;EACxG,OAAO;GAAE,OAAO,CAAC;GAAG,UAAU,MAAM;GAAU,aAAa,MAAM,eAAe,KAAA;EAAU;CAC3F;CACA,IAAI,CAAC,oBAAoB,WAAW,GACnC,OAAO,QAAQ,+BAA+B,QAAQ,YAAY,QAAQ,cAAc,OAAO,CAAC;CAEjG,IAAI,CAAC,YAAY,iCAChB,OAAO,QACN,aACC,QAAQ,YACR,KAAA,GACA,QAAQ,cACR,GAAG,QAAQ,wBAAwB,QAAQ,WAAW,wFACvD,CACD;CAMD,IACC,qCAAqC,QAAQ,UAAU,KACvD,CAAC,qBAAqB,QAAQ,YAAY,YAAY,MAAM,GAE5D,OAAO,QACN,aACC,QAAQ,YACR,KAAA,GACA,QAAQ,cACR,GAAG,QAAQ,gCAAgC,QAAQ,WAAW,yCAC/D,CACD;CAGD,MAAM,SAAS,IAAI,cAAc,aAAa,QAAQ,YAAY,QAAQ,cAAc,QAAQ,MAAM;CACtG,MAAM,QAAQ,MAAM,YACnB,QAAQ,YACR,QACA,QAAQ,oBAEP,YAAY,2BAA2B,QAAQ,YAAY,QAAQ,KAAK;EACvE,cAAc,QAAQ;EACT;CACd,CAAC,GACF,EAAE,sBAAsB,KAAK,CAC9B;CACA,IAAI,MAAM,WAAW,MACpB,OAAO,QAAQ,MAAM,OAAO;CAG7B,OAAO;EACN,OAAO,CAAC;GAAE,KAAK,QAAQ;GAAK,GAAI,MAAM,SAAS,OAAO,EAAE,OAAO,MAAM,MAAM,IAAI,CAAC;EAAG,CAAC;EACpF,UAAU,CAAC;CACZ;AACD"}