@gravitee/gamma-lib-observability 6.3.0 → 6.4.0

package/INTEGRATION.md

@@ -1279,25 +1279,27 @@ Capabilities say what the host allows in general; the backend's ACLs decide per
 
 Refusals are remembered **per verb family** (read, write), not per operation: one refused delete withdraws every authoring affordance — create, edit and delete alike — until some write succeeds or the section remounts. If your ACL model routinely grants partial write sets, expect that coarseness.
 
-A store that enforces permissions must reject with `DashboardForbiddenError` (or a `status: 403` error) for the degradation to engage — see the port's documentation. Only a 403 earns the quiet degradation: any other listing failure is a fault, not a designed experience (its current silence on the list is a known gap).
+A store that enforces permissions must reject with `DashboardForbiddenError` (or a `status: 403` error) for the degradation to engage — see the port's documentation. Only a 403 earns the quiet degradation: any other listing failure is a fault, and the list says so above its table ("Couldn't load custom dashboards.", with "Try again" and "View details"), the templates still listed.
 
 #### Refused data (logs, traces, analytics, filters)
 
 The same rule holds for the data behind the screens. The built-in HTTP sources reject a failed call with an `ObservabilityHttpError` that keeps the HTTP `status`; `isForbiddenError(error)` tells a refusal from any other failure, reading the status from the shape so a host source's own errors (anything with `status: 403`) count too. A refusal is named where it happened, never offered a retry, and never shown as "no data". Every refusal uses the same component, `AccessDeniedState`, so the reader is guided the same way everywhere: the title names the data, and the description is always "Ask an administrator for access." Its `compact` variant (a chart's area, dashboard tiles) drops the description by itself when its box is too short; its `inline` variant fits next to a control.
 
-| Where                          | On a refusal                                                                                               | On any other failure                      |
-| ------------------------------ | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
-| Logs page, logs table          | Headers kept; "No access to logs" where "No logs found" would be                                           | Error banner with Retry (unchanged)       |
-| Logs page, chart               | "No access to analytics" in the chart's area, at its height                                                | The chart's empty state (unchanged)       |
-| Logs page, both refused        | One "No access to logs and analytics" for the page, in place of chart and table; no filters or time range  | Each part as above                        |
-| Log detail chart               | "No access to analytics" in the chart's place                                                              | The chart's empty state (unchanged)       |
-| Traces table                   | Headers kept; "No access to traces" in the empty rows; no filters or time range                            | Error banner with Retry (unchanged)       |
-| Log and trace detail           | "No access to this log" / "No access to this trace"                                                        | Error with Retry (unchanged)              |
-| A dashboard widget             | "No access to analytics" (or logs, traces) in that tile only, when the dashboard is mixed                  | The widget's empty state (unchanged)      |
-| A whole dashboard              | One state named after the refused kinds, in place of the widget grid; title kept, no filters or time range | Each widget as above                      |
-| Filter bar (both filter lists) | "No access to filters." inline, next to the disabled "Add filter"                                          | "Filters could not be loaded." with Retry |
-| Tracing API picker (paginated) | "No access to APIs." inline, next to the field                                                             | "Failed to load APIs. Try again."         |
-| Filter values                  | Falls back to typing the value, as for any listing failure                                                 | Same (unchanged)                          |
+| Where                             | On a refusal                                                                                               | On any other failure                                                                       |
+| --------------------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
+| Logs page, logs table             | Headers kept; "No access to logs" where "No logs found" would be                                           | "Couldn't load logs" in the empty rows                                                     |
+| Logs page, chart                  | "No access to analytics" in the chart's area, at its height                                                | "Couldn't load analytics" in its area                                                      |
+| Logs page, both refused           | One "No access to logs and analytics" for the page, in place of chart and table; no filters or time range  | Both failed: one state with Try again                                                      |
+| Log detail chart                  | "No access to analytics" in the chart's place                                                              | "Couldn't load analytics" in its place                                                     |
+| Traces table                      | Headers kept; "No access to traces" in the empty rows; no filters or time range                            | "Couldn't load traces" with Try again                                                      |
+| Log and trace detail              | "No access to this log" / "No access to this trace"                                                        | "Couldn't load this log" with Try again                                                    |
+| A dashboard widget                | "No access to analytics" (or logs, traces) in that tile only, when the dashboard is mixed                  | "Couldn't load analytics" in that tile                                                     |
+| A whole dashboard                 | One state named after the refused kinds, in place of the widget grid; title kept, no filters or time range | All failed: one state with Try again                                                       |
+| Filter bar (both filter lists)    | "No access to filters." inline, next to the disabled "Add filter"                                          | "Couldn't load filters." with Try again                                                    |
+| Tracing API picker (paginated)    | "No access to APIs." inline, next to the field                                                             | "Couldn't load APIs." with Try again                                                       |
+| Filter values                     | Falls back to typing the value, with "No access to these values." under the field                          | Falls back to typing the value, with "Couldn't load values." and Try again under the field |
+| A custom dashboard (page, editor) | "No access to this dashboard"; the editor keeps "Back to dashboards"                                       | "Couldn't load this dashboard" with Try again                                              |
+| Dashboards list                   | Read-only template experience, no error                                                                    | "Couldn't load custom dashboards." with Try again, above the templates                     |
 
 **404 that may stand for a refusal.** The trace search, trace detail and log detail endpoints answer 404 for an API the reader may not see, so that its existence does not leak. These three screens keep that promise: on a 404 (`isNotFoundError`), and on a log detail the source reports as missing, they show "API not found, or you don't have access" (in the traces table), "Trace not found, …" or "Log not found, …", with "Check the link, or ask an administrator for access.", and no retry. A 404 anywhere else keeps its existing handling.
 
@@ -1307,19 +1309,35 @@ An empty answer is not a refusal: a reader whose APIs have no traffic in range,
 
 **Retries.** The library's queries run on the host's `QueryClient`, and its `retry` setting still applies to failures (5xx, network). A 4xx answer is never retried: the server answered on purpose, so the screen says so at once instead of showing skeletons through every retry.
 
+### Load failures (5xx, network)
+
+A failure that is not a refusal (a 5xx, a network error, a host source's own error) is shown the same way everywhere, with `LoadFailedState`, the sibling of `AccessDeniedState`: same variants and the same layout (an icon, a title naming the data, one line under it), nothing in red, and in the data's own place, so a failure never reads as an empty answer and never sits above one. The table above lists where. "No data" and "No logs found" are for empty answers only.
+
+- **Wording.** The title names the data: "Couldn't load logs", "Couldn't load analytics", "Couldn't load traces", "Couldn't load this log", "Couldn't load this trace". A compact state (a tile, a chart's area) shows the title alone. While Live is on, a state whose data follows the Live window (`followsLive`) counts down to the refresh that loads it again: "Trying again in 42 seconds.", and a page-level state's button reads "Try now". Otherwise (Live paused, an absolute range, a log or trace opened by id) a page-level state says "Something went wrong. Try again in a moment." with "Try again".
+- **A failed refetch keeps what is on screen, everywhere.** Live data keeps its earlier answer and the Live pill says so; a log or a trace opened by id keeps showing when a background refetch fails (the detail hooks' `isError` means "failed with nothing to show"); a filter list asked again keeps the screens, its failure saying "Trying again…" (`FilterCatalogLoad.retrying`), never the first-load skeleton.
+- **No flicker between two failures.** While the same question is asked again (the next Live refresh, "Try again"), the failure stays on screen until an answer comes back, rather than flashing a loading state; the details stay open. Meanwhile the state says "Trying again…" in place of its countdown, its button pending (`LoadFailure.retrying`, set by the library's hooks; a host passes `retrying` to `WidgetLoadFailed`).
+- **One retry per page.** One part of a page failing (a widget tile, the logs chart or the logs table, the log detail's chart) gets no retry: the rest of the page still works and the next refresh asks again. A page whose every part failed gets exactly one "Try again", which re-runs every failed query on screen: the traces page, a log or trace detail (a drawer included), the logs page with both parts failed (one state, "Couldn't load logs and analytics"), the logs page without a chart, a dashboard whose every widget failed. The filter bar, the tracing API picker and the message list of a log detail keep their own inline "Try again": Live mode refreshes the data, never those lists.
+- **One state for a page.** A dashboard shows one state for all of it only when every widget has the same outcome, all refused or all failed, in place of its grid. Any mix, a refused widget next to a failed one included, keeps a state per tile. On the Logs page, a refusal on one side and a failure on the other stay each in place. Unlike a refusal, a failure keeps the filters and the time range: it may depend on them.
+- **Details on demand.** A state's "View details" opens a side panel with each failed call: its status, the call, what went wrong in words and when it failed, and "Copy for support", which copies exactly that as text. The words are labelled "Server message", in monospace, when they are what the server said in its answer (the `message`, `detail` or `error` of a JSON body, or a short plain-text body; never an HTML error page), kept as `ObservabilityHttpError.detail`. The Management API answers with the exception's message only, never its stack: a failed search answers `{ "message": "Unable to search", "http_status": 500 }`, what its Elasticsearch client says for any search that fails, and an invalid request names the problem ("Value 'abc' is not a whole number, as filter 'HTTP_STATUS' requires", on a 400). A call that got no response shows "Error" with the error it ended on, such as "Failed to fetch". Every form of the state, a tile, a chart's area and a line next to a control included, offers the same "View details". There is no request id: the sources read no response headers. `ObservabilityHttpError` carries the `call` for this; a host source's error with a `status` and a `call` is described the same way. The `[gamma-lib-observability]` prefix of the error message stays in console logs.
+- **A failed refresh keeps the data.** Live mode refetches every minute by moving the window forward, and switching Paused back to Live refetches at once, on every page, the data Live keeps fresh only (analytics, logs and traces searches): a log or a trace open in a drawer, a filter list or a dashboard definition is not reloaded. When a refresh fails with data on screen, the data stays and the Live pill says so: an amber dot, and "Couldn't refresh at HH:MM. Showing earlier data." in its tooltip. That is the page's one signal of stale data, never a failure state over good data. A change of filters or time range is a new question: if it fails, the failure is shown, never the old data. A refusal never keeps old data either.
+- **Host widgets.** A host widget renderer shows its failure with `WidgetLoadFailed` (`error`, `failedAt`, and `dataKind` for logs or traces), which also lets the dashboard show one state when every widget failed. Pass the query's own `error`: the same object from one render to the next.
+
+`QueryErrorBanner` stays exported for hosts that render it, but the library's pages no longer use it.
+
 **Try it.** The Storybook story `Routing/Permissions › Playground` renders every observability page through the real routes against mock sources. Its controls reach each case above without code, and default to everything allowed. Changing a right refreshes the page you are on, and navigating in the story's sidebar moves the Page control along:
 
-| Control                                                               | Values                                                   | What it drives                                                           |
-| --------------------------------------------------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------ |
-| Page                                                                  | Home, Dashboard, Logs, Log detail, Tracing, Trace detail | The page the reader opens (Home: the section root)                       |
-| Analytics                                                             | Allowed, Refused (403), Failing (500)                    | Dashboard widgets, the logs histogram, the log detail chart              |
-| Logs                                                                  | Allowed, Refused (403), Failing (500)                    | The logs table, a log detail, the dashboard's logs widget                |
-| Traces                                                                | Allowed, Refused (403), Failing (500)                    | The traces table and a trace detail                                      |
-| API the reader may not see                                            | on / off                                                 | The deliberate 404 on the tracing page, a trace detail and a log detail  |
-| Filter lists                                                          | Allowed, Refused (403), Failing (500)                    | The filter bar's filter lists (analytics and tracing)                    |
-| Tracing API list                                                      | Allowed, Refused (403), Failing (500)                    | The tracing API picker                                                   |
-| Capability: dashboards.read, dashboards.write, logs.read, traces.read | on / off                                                 | The host's capabilities: which sections exist, in the nav and the routes |
-| Dashboard with a logs widget                                          | on / off                                                 | Adds a host widget backed by logs, for a dashboard mixing data kinds     |
+| Control                                                               | Values                                                   | What it drives                                                                                                        |
+| --------------------------------------------------------------------- | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| Page                                                                  | Home, Dashboard, Logs, Log detail, Tracing, Trace detail | The page the reader opens (Home: the section root)                                                                    |
+| Analytics                                                             | Allowed, Refused (403), Failing (500), Partly failing    | Dashboard widgets, the logs histogram, the log detail chart; partly: the breakdowns fail, time series and totals load |
+| Failed refresh                                                        | on / off                                                 | Data loads, then every refresh fails: the Live pill turns amber                                                       |
+| Logs                                                                  | Allowed, Refused (403), Failing (500)                    | The logs table, a log detail, the dashboard's logs widget                                                             |
+| Traces                                                                | Allowed, Refused (403), Failing (500)                    | The traces table and a trace detail                                                                                   |
+| API the reader may not see                                            | on / off                                                 | The deliberate 404 on the tracing page, a trace detail and a log detail                                               |
+| Filter lists                                                          | Allowed, Refused (403), Failing (500)                    | The filter bar's filter lists (analytics and tracing)                                                                 |
+| Tracing API list                                                      | Allowed, Refused (403), Failing (500)                    | The tracing API picker                                                                                                |
+| Capability: dashboards.read, dashboards.write, logs.read, traces.read | on / off                                                 | The host's capabilities: which sections exist, in the nav and the routes                                              |
+| Dashboard with a logs widget                                          | on / off                                                 | Adds a host widget backed by logs, for a dashboard mixing data kinds                                                  |
 
 **Concurrent edits.** `DashboardConflictError` carries `currentDashboard`, the dashboard as it now stands in the store, and the editor renders it from there rather than fetching again. The author then picks one of three resolutions, and each comes back to this port:
 

package/dist/components/FailureDetailsSheet.d.ts

@@ -0,0 +1,13 @@
+import { LoadFailure } from './failure-wording';
+export interface FailureDetailsSheetProps {
+    readonly failures: readonly LoadFailure[];
+    readonly open: boolean;
+    readonly onOpenChange: (open: boolean) => void;
+}
+/**
+ * The technical side of a failure, one step away from the page: each failed
+ * call with its status, the call, what the server said about it and when it
+ * failed, and a copy of exactly that as text for a support ticket.
+ */
+export declare function FailureDetailsSheet({ failures, open, onOpenChange }: FailureDetailsSheetProps): import("react/jsx-runtime").JSX.Element;
+//# sourceMappingURL=FailureDetailsSheet.d.ts.map

package/dist/components/FailureDetailsSheet.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"FailureDetailsSheet.d.ts","sourceRoot":"","sources":["../../src/components/FailureDetailsSheet.tsx"],"names":[],"mappings":"AAYA,OAAO,EAML,KAAK,WAAW,EACjB,MAAM,mBAAmB,CAAC;AAE3B,MAAM,WAAW,wBAAwB;IACvC,QAAQ,CAAC,QAAQ,EAAE,SAAS,WAAW,EAAE,CAAC;IAC1C,QAAQ,CAAC,IAAI,EAAE,OAAO,CAAC;IACvB,QAAQ,CAAC,YAAY,EAAE,CAAC,IAAI,EAAE,OAAO,KAAK,IAAI,CAAC;CAChD;AAcD;;;;GAIG;AACH,wBAAgB,mBAAmB,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,YAAY,EAAE,EAAE,wBAAwB,2CAkC7F"}

package/dist/components/LoadFailedState.d.ts

@@ -0,0 +1,40 @@
+import { ReactNode } from 'react';
+import { AccessDeniedStateVariant } from './AccessDeniedState';
+import { LoadFailure } from './failure-wording';
+/** The same three as a refusal: a page or a table's rows, a small box, one line next to a control. */
+export type LoadFailedStateVariant = AccessDeniedStateVariant;
+export interface LoadFailedStateProps {
+    /** What did not load, naming the data: "Couldn't load logs". */
+    readonly title: string;
+    /** The failures behind it, described on demand for support. */
+    readonly failures?: readonly LoadFailure[];
+    /**
+     * Given to a page-level state only: re-runs the page's failed loads, and
+     * adds the guidance that goes with it. One part of a page failing gets no
+     * retry: the next refresh asks again, and the rest of the page still works.
+     */
+    readonly onRetry?: () => void;
+    /**
+     * The data loads again on its own at each Live refresh (a query built on the
+     * Live window): the state counts down to the next one while Live is on.
+     * Leave it off for data Live never reloads, such as a log opened by id.
+     * @default false
+     */
+    readonly followsLive?: boolean;
+    /** Rendered next to the retry, e.g. a way back. Shown by the default form only, like a refusal's. */
+    readonly action?: ReactNode;
+    /** @default 'default' */
+    readonly variant?: LoadFailedStateVariant;
+    readonly className?: string;
+}
+/**
+ * What a screen shows in place of data that failed to load (5xx, network).
+ * Every failure in the library uses it, in the data's own place, so a failure
+ * never reads as an empty answer. The sibling of `AccessDeniedState`, laid out
+ * the same way so a failure and a refusal read alike: an icon, a title naming
+ * the data, one line under it. Neutral, nothing in red, and the technical
+ * details one step away: every form, down to a tile or a line next to a
+ * control, offers the same "View details" and its side panel.
+ */
+export declare function LoadFailedState({ title, failures, onRetry, followsLive, action, variant, className, }: LoadFailedStateProps): import("react/jsx-runtime").JSX.Element;
+//# sourceMappingURL=LoadFailedState.d.ts.map

package/dist/components/LoadFailedState.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"LoadFailedState.d.ts","sourceRoot":"","sources":["../../src/components/LoadFailedState.tsx"],"names":[],"mappings":"AAWA,OAAO,EAAmB,KAAK,SAAS,EAAE,MAAM,OAAO,CAAC;AAExD,OAAO,KAAK,EAAE,wBAAwB,EAAE,MAAM,qBAAqB,CAAC;AAEpE,OAAO,EAA8C,KAAK,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEjG,sGAAsG;AACtG,MAAM,MAAM,sBAAsB,GAAG,wBAAwB,CAAC;AAE9D,MAAM,WAAW,oBAAoB;IACnC,gEAAgE;IAChE,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,+DAA+D;IAC/D,QAAQ,CAAC,QAAQ,CAAC,EAAE,SAAS,WAAW,EAAE,CAAC;IAC3C;;;;OAIG;IACH,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,IAAI,CAAC;IAC9B;;;;;OAKG;IACH,QAAQ,CAAC,WAAW,CAAC,EAAE,OAAO,CAAC;IAC/B,qGAAqG;IACrG,QAAQ,CAAC,MAAM,CAAC,EAAE,SAAS,CAAC;IAC5B,yBAAyB;IACzB,QAAQ,CAAC,OAAO,CAAC,EAAE,sBAAsB,CAAC;IAC1C,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC;CAC7B;AAED;;;;;;;;GAQG;AACH,wBAAgB,eAAe,CAAC,EAC9B,KAAK,EACL,QAAQ,EACR,OAAO,EACP,WAAmB,EACnB,MAAM,EACN,OAAmB,EACnB,SAAS,GACV,EAAE,oBAAoB,2CAmBtB"}

package/dist/components/QueryErrorBanner.d.ts

@@ -7,9 +7,11 @@ export interface QueryErrorBannerProps {
 }
 /**
  * Inline error banner for a failed data query. Exposed with `role="alert"` so
- * assistive technologies announce the failure as soon as it renders. Shared by
- * the observability explorer pages so logs and traces surface query errors
- * identically.
+ * assistive technologies announce the failure as soon as it renders.
+ *
+ * The library's own pages no longer use it: they show `LoadFailedState` in the
+ * data's own place, so a failure never sits above an empty table. Kept for
+ * hosts that still render it.
  */
 export declare function QueryErrorBanner({ message, onRetry, className }: QueryErrorBannerProps): import("react/jsx-runtime").JSX.Element;
 //# sourceMappingURL=QueryErrorBanner.d.ts.map

package/dist/components/QueryErrorBanner.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"QueryErrorBanner.d.ts","sourceRoot":"","sources":["../../src/components/QueryErrorBanner.tsx"],"names":[],"mappings":"AAGA,MAAM,WAAW,qBAAqB;IACpC,2DAA2D;IAC3D,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,0CAA0C;IAC1C,QAAQ,CAAC,OAAO,EAAE,MAAM,IAAI,CAAC;IAC7B,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC;CAC7B;AAED;;;;;GAKG;AACH,wBAAgB,gBAAgB,CAAC,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,EAAE,qBAAqB,2CAiBtF"}
+{"version":3,"file":"QueryErrorBanner.d.ts","sourceRoot":"","sources":["../../src/components/QueryErrorBanner.tsx"],"names":[],"mappings":"AAGA,MAAM,WAAW,qBAAqB;IACpC,2DAA2D;IAC3D,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IACzB,0CAA0C;IAC1C,QAAQ,CAAC,OAAO,EAAE,MAAM,IAAI,CAAC;IAC7B,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC;CAC7B;AAED;;;;;;;GAOG;AACH,wBAAgB,gBAAgB,CAAC,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,EAAE,qBAAqB,2CAiBtF"}

package/dist/components/failure-wording.d.ts

@@ -0,0 +1,61 @@
+import { DataKind } from './refusal-wording';
+/** A failed load, with when it failed: what a failure state's details describe. */
+export interface LoadFailure {
+    readonly error: unknown;
+    /** When the load failed, in epoch milliseconds, when known. */
+    readonly at?: number;
+    /**
+     * The same data is being loaded again right now (a retry, a Live refresh):
+     * the state says so while it waits, rather than looking unchanged.
+     */
+    readonly retrying?: boolean;
+}
+/**
+ * What a page-level failure state says under its title, next to its one "Try
+ * again", when nothing will load the data again on its own.
+ */
+export declare const FAILURE_GUIDANCE = "Something went wrong. Try again in a moment.";
+/**
+ * The title of a failure, naming what did not load: "Couldn't load analytics",
+ * or every kind once when several parts failed, "Couldn't load logs and
+ * analytics".
+ */
+export declare function failureTitle(kinds: Iterable<DataKind>): string;
+/** What is known of one failed call, for the details. */
+export interface FailureFacts {
+    /** The HTTP status, absent when no response came back. */
+    readonly status?: number;
+    /** The call that failed, "POST /observability/logs/search", when known. */
+    readonly call?: string;
+    /**
+     * What went wrong in words: what the server said about it, or without a
+     * response, the error's own message (a network failure, a timeout, a host
+     * source's error).
+     */
+    readonly message?: string;
+    readonly at?: number;
+}
+/**
+ * Each distinct failed call, the latest when the same call failed several
+ * times. No request id: the sources read no response headers.
+ */
+export declare function failureFacts(failures: readonly LoadFailure[]): FailureFacts[];
+/** "HTTP 500", or "No response" when nothing came back. */
+export declare function failureStatusLabel(status: number | undefined): string;
+/**
+ * What the words of a failure are: what the server said in its answer, or,
+ * when no answer came, the error the call ended on ("Failed to fetch").
+ */
+export declare function failureMessageLabel(status: number | undefined): string;
+/** "Today, 10:42:13", or the date as well on another day. */
+export declare function formatFailureTime(at: number, now?: number): string;
+/**
+ * The technical details of one or several failures as text, for a support
+ * ticket: the status, the call and the time of each distinct failed call.
+ */
+export declare function describeFailures(failures: readonly LoadFailure[]): string;
+/** What a failure state says while the data is being loaded again. */
+export declare const RETRYING = "Trying again\u2026";
+/** What a failure state says while Live mode is about to load the data again. */
+export declare function retryCountdown(seconds: number): string;
+//# sourceMappingURL=failure-wording.d.ts.map

package/dist/components/failure-wording.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"failure-wording.d.ts","sourceRoot":"","sources":["../../src/components/failure-wording.ts"],"names":[],"mappings":"AAEA,OAAO,EAAiB,KAAK,QAAQ,EAAE,MAAM,mBAAmB,CAAC;AAEjE,mFAAmF;AACnF,MAAM,WAAW,WAAW;IAC1B,QAAQ,CAAC,KAAK,EAAE,OAAO,CAAC;IACxB,+DAA+D;IAC/D,QAAQ,CAAC,EAAE,CAAC,EAAE,MAAM,CAAC;IACrB;;;OAGG;IACH,QAAQ,CAAC,QAAQ,CAAC,EAAE,OAAO,CAAC;CAC7B;AAED;;;GAGG;AACH,eAAO,MAAM,gBAAgB,iDAAiD,CAAC;AAE/E;;;;GAIG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,QAAQ,CAAC,QAAQ,CAAC,GAAG,MAAM,CAE9D;AAYD,yDAAyD;AACzD,MAAM,WAAW,YAAY;IAC3B,0DAA0D;IAC1D,QAAQ,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC;IACzB,2EAA2E;IAC3E,QAAQ,CAAC,IAAI,CAAC,EAAE,MAAM,CAAC;IACvB;;;;OAIG;IACH,QAAQ,CAAC,OAAO,CAAC,EAAE,MAAM,CAAC;IAC1B,QAAQ,CAAC,EAAE,CAAC,EAAE,MAAM,CAAC;CACtB;AAqBD;;;GAGG;AACH,wBAAgB,YAAY,CAAC,QAAQ,EAAE,SAAS,WAAW,EAAE,GAAG,YAAY,EAAE,CAQ7E;AAED,2DAA2D;AAC3D,wBAAgB,kBAAkB,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,CAErE;AAED;;;GAGG;AACH,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,MAAM,GAAG,SAAS,GAAG,MAAM,CAEtE;AAED,6DAA6D;AAC7D,wBAAgB,iBAAiB,CAAC,EAAE,EAAE,MAAM,EAAE,GAAG,GAAE,MAAmB,GAAG,MAAM,CAI9E;AAUD;;;GAGG;AACH,wBAAgB,gBAAgB,CAAC,QAAQ,EAAE,SAAS,WAAW,EAAE,GAAG,MAAM,CAEzE;AAED,sEAAsE;AACtE,eAAO,MAAM,QAAQ,uBAAkB,CAAC;AAExC,iFAAiF;AACjF,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CAEtD"}

package/dist/components/index.d.ts

@@ -1,5 +1,8 @@
 export { AccessDeniedState } from './AccessDeniedState';
 export type { AccessDeniedStateProps, AccessDeniedStateVariant } from './AccessDeniedState';
+export { LoadFailedState } from './LoadFailedState';
+export type { LoadFailedStateProps, LoadFailedStateVariant } from './LoadFailedState';
+export type { LoadFailure } from './failure-wording';
 export { QueryErrorBanner } from './QueryErrorBanner';
 export type { QueryErrorBannerProps } from './QueryErrorBanner';
 //# sourceMappingURL=index.d.ts.map

package/dist/components/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/components/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,qBAAqB,CAAC;AACxD,YAAY,EAAE,sBAAsB,EAAE,wBAAwB,EAAE,MAAM,qBAAqB,CAAC;AAC5F,OAAO,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAC;AACtD,YAAY,EAAE,qBAAqB,EAAE,MAAM,oBAAoB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/components/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,iBAAiB,EAAE,MAAM,qBAAqB,CAAC;AACxD,YAAY,EAAE,sBAAsB,EAAE,wBAAwB,EAAE,MAAM,qBAAqB,CAAC;AAC5F,OAAO,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AACpD,YAAY,EAAE,oBAAoB,EAAE,sBAAsB,EAAE,MAAM,mBAAmB,CAAC;AACtF,YAAY,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AACrD,OAAO,EAAE,gBAAgB,EAAE,MAAM,oBAAoB,CAAC;AACtD,YAAY,EAAE,qBAAqB,EAAE,MAAM,oBAAoB,CAAC"}

package/dist/components/refusal-wording.d.ts

@@ -1,9 +1,14 @@
 /**
- * The kinds of data a reader may be refused, one per right: analytics
- * (`API_ANALYTICS`), logs and traces (`API_LOG`). A refusal names the kind, so
- * the reader knows which access to ask for.
+ * The kinds of data a screen reads, one per right: analytics
+ * (`API_ANALYTICS`), logs and traces (`API_LOG`). A refusal or a failure
+ * names the kind, so the reader knows which access to ask for, or what is
+ * missing from the screen.
  */
-export type RefusedDataKind = 'logs' | 'traces' | 'analytics';
+export type DataKind = 'logs' | 'traces' | 'analytics';
+/** The kinds of data a reader may be refused. */
+export type RefusedDataKind = DataKind;
+/** Every kind once, in a stable order: "logs, traces and analytics". */
+export declare function listDataKinds(kinds: Iterable<DataKind>): string;
 /**
  * The title of a refusal: "No access to analytics", or every refused kind once,
  * "No access to logs and analytics", so asking for one of them is not mistaken

package/dist/components/refusal-wording.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"refusal-wording.d.ts","sourceRoot":"","sources":["../../src/components/refusal-wording.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AACH,MAAM,MAAM,eAAe,GAAG,MAAM,GAAG,QAAQ,GAAG,WAAW,CAAC;AAK9D;;;;GAIG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,QAAQ,CAAC,eAAe,CAAC,GAAG,MAAM,CAMrE"}
+{"version":3,"file":"refusal-wording.d.ts","sourceRoot":"","sources":["../../src/components/refusal-wording.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AACH,MAAM,MAAM,QAAQ,GAAG,MAAM,GAAG,QAAQ,GAAG,WAAW,CAAC;AAEvD,iDAAiD;AACjD,MAAM,MAAM,eAAe,GAAG,QAAQ,CAAC;AAKvC,wEAAwE;AACxE,wBAAgB,aAAa,CAAC,KAAK,EAAE,QAAQ,CAAC,QAAQ,CAAC,GAAG,MAAM,CAK/D;AAED;;;;GAIG;AACH,wBAAgB,YAAY,CAAC,KAAK,EAAE,QAAQ,CAAC,eAAe,CAAC,GAAG,MAAM,CAErE"}