npm - @malloy-publisher/server - Versions diffs - 0.0.248 → 0.0.250 - Mend

@malloy-publisher/server 0.0.248 → 0.0.250

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (29) hide show

package/README.docker.md CHANGED Viewed

@@ -1,3 +1,8 @@
+<!--
+Copyright (c) Credible Data Inc.
+SPDX-License-Identifier: MIT
+-->
 # Publisher in Docker
 The canonical build is the root [`Dockerfile`](../../Dockerfile) and the CI smoke test (`docker_smoke_test` in `.github/workflows/build.yml`) builds and runs that exact image. The two-port REST + MCP server, the Snowflake ADBC driver, the DuckDB CLI, and the production app bundle all ship in it.

package/README.md CHANGED Viewed

@@ -1,3 +1,8 @@
+<!--
+Copyright (c) Credible Data Inc.
+SPDX-License-Identifier: MIT
+-->
 # Malloy Publisher Server
 The Malloy Publisher Server is an Express.js server that provides an API for managing and accessing Malloy data models, packages, and queries

package/dist/app/api-doc.html CHANGED Viewed

@@ -1,4 +1,9 @@
 <!doctype html>
+<!--
+Copyright (c) Credible Data Inc.
+SPDX-License-Identifier: MIT
+-->
 <html lang="en">
    <head>
       <meta charset="utf-8" />

package/dist/app/api-doc.yaml CHANGED Viewed

@@ -1,3 +1,6 @@
+# Copyright (c) Credible Data Inc.
+# SPDX-License-Identifier: MIT
 openapi: 3.1.0
 info:
   title: Malloy Publisher - Semantic Model Serving API
@@ -64,6 +67,10 @@ tags:
     description: Malloy model access and compilation operations
   - name: notebooks
     description: Malloy notebook access and execution operations
+  - name: dashboards
+    description:
+      Discovery and manifests for `# artifact` dashboards - layout, tiles, and
+      the given specs behind their controls
   - name: data-apps
     description:
       In-package HTML data apps (static pages served from a package's public/
@@ -1715,6 +1722,150 @@ paths:
         "503":
           $ref: "#/components/responses/ServiceUnavailable"
+  /environments/{environmentName}/packages/{packageName}/dashboards:
+    get:
+      tags:
+        - dashboards
+      operationId: list-dashboards
+      summary: List package dashboards
+      description: |
+        Lists the dashboards in the specified package — every `.malloy` file in
+        the package's `dashboards/` directory that carries an `# artifact` (or
+        model-level `## artifact`) annotation. A file in that directory with no
+        artifact tag is a shared include and is not listed, whether or not it
+        compiles.
+        A tagged dashboard that failed to compile is listed carrying its
+        `error` where that state can arise at all, so a broken dashboard is
+        visibly broken rather than silently absent. In practice it rarely does:
+        a package whose model fails to compile is not loaded, and a reload that
+        would break one is refused and leaves the previously loaded package
+        serving, so `error` is only reachable on the paths that keep per-model
+        placeholders. Treat it as present-but-uncommon rather than the normal
+        way a broken dashboard surfaces. When the package curates its query surface
+        (`queryableSources: "declared"`), a dashboard whose entry file is not in
+        `explores` is omitted, because its query and given names would not be
+        runnable; the omission is reported in the package's `warnings` as of the
+        last load. A metadata `PATCH` that TIGHTENS curation takes effect on
+        this listing immediately; one that relaxes it takes effect on the next
+        package reload, because the withheld dashboards were never built into
+        the cached set. Either way the matching warning is computed at load, so
+        after a `PATCH` it appears only once the package reloads.
+        Where the boundary is active at all, which needs `explores` declared
+        AND `queryableSources` left at `"declared"`, being listed does not by
+        itself guarantee the dashboard runs: the queryable sources are the
+        union of every listed file's `export {}` closure, so a dashboard whose
+        tiles read a source that only an UNLISTED file exports is still served
+        while those queries are refused. The fix is to list that file too, or
+        to re-export the source from one already listed. It is served rather
+        than withheld because withholding on a guess would hide dashboards that
+        do work. Under `"all"` nothing is refused, so the situation does not
+        arise.
+      parameters:
+        - name: environmentName
+          in: path
+          description: Name of the environment
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: packageName
+          in: path
+          description: Name of the package
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: versionId
+          in: query
+          description: Version identifier for the package
+          required: false
+          schema:
+            $ref: "#/components/schemas/VersionIdPattern"
+      responses:
+        "200":
+          description: A list of dashboards in the package
+          content:
+            application/json:
+              schema:
+                type: array
+                items:
+                  $ref: "#/components/schemas/Dashboard"
+        "401":
+          $ref: "#/components/responses/Unauthorized"
+        "404":
+          $ref: "#/components/responses/NotFound"
+        "500":
+          $ref: "#/components/responses/InternalServerError"
+        "501":
+          $ref: "#/components/responses/NotImplemented"
+        "503":
+          $ref: "#/components/responses/ServiceUnavailable"
+  /environments/{environmentName}/packages/{packageName}/dashboards/{dashboardName}:
+    get:
+      tags:
+        - dashboards
+      operationId: get-dashboard
+      summary: Get a dashboard manifest
+      description: |
+        Retrieves everything a viewer needs to render one dashboard: the artifact
+        tag's declarations plus the control contract derived from the givens its
+        query references. Running the dashboard needs no further endpoint — its
+        query, each composite tile, and each control's suggest query all run
+        through the model query endpoint with `givens`, using the manifest's
+        `path` as the model.
+      parameters:
+        - name: environmentName
+          in: path
+          description: Name of the environment
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: packageName
+          in: path
+          description: Name of the package
+          required: true
+          schema:
+            $ref: "#/components/schemas/IdentifierPattern"
+        - name: dashboardName
+          in: path
+          description: >-
+            The dashboard's name: its filename basename. Conventionally letters,
+            digits, "-" and "_", and a package is warned when one of its SERVED
+            dashboards falls outside that. A dashboard withheld by curation gets
+            no naming finding, because the naming check runs after the curation
+            gate and a withheld dashboard is already reported as withheld. It is NOT constrained to it, because
+            the name comes from a filename rather than being chosen: a file such
+            as `dashboards/v1.2.malloy` is served, and its published `resource`
+            carries the name percent-encoded. Send it percent-encoded.
+          required: true
+          schema:
+            type: string
+            minLength: 1
+        - name: versionId
+          in: query
+          description: Version identifier for the package
+          required: false
+          schema:
+            $ref: "#/components/schemas/VersionIdPattern"
+      responses:
+        "200":
+          description: The dashboard manifest
+          content:
+            application/json:
+              schema:
+                $ref: "#/components/schemas/DashboardManifest"
+        "401":
+          $ref: "#/components/responses/Unauthorized"
+        "404":
+          $ref: "#/components/responses/NotFound"
+        "500":
+          $ref: "#/components/responses/InternalServerError"
+        "501":
+          $ref: "#/components/responses/NotImplemented"
+        "503":
+          $ref: "#/components/responses/ServiceUnavailable"
   /environments/{environmentName}/packages/{packageName}/notebooks:
     get:
       tags:
@@ -2854,9 +3005,19 @@ components:
             collision, and materialization-config problems that degrade
             attribution. Discovery findings: a model listed in `explores` whose
             export closure surfaces no sources or named queries, so it lists as
-            empty and renders a blank page. Server-computed and read-only:
-            ignored on create/update requests and only returned in responses.
-            Present only when there are such findings.
+            empty and renders a blank page. Dashboard findings: a
+            `dashboards/` file whose `# artifact` tag does not parse or does not
+            describe a dashboard, a tile or suggest query that does not resolve,
+            a `# drill` naming a destination that is not a dashboard, and a
+            dashboard held back from the listing because its entry file is not
+            in `explores`. Two dashboard findings are about Publisher rather
+            than about the package: one when a file carrying an artifact tag
+            could not be read and so is not served at all, and one when the lint
+            stops early, in which case the list must be read as incomplete
+            rather than as a clean package. Server-computed and read-only:
+            ignored on
+            create/update requests and only returned in responses. Present only
+            when there are such findings.
             **Pre-aggregation contributes nothing to this array. A
@@ -2913,9 +3074,13 @@ components:
                 type: string
                 description: >-
                   What the finding is about: the query or view a render finding
-                  sits on (`by_carrier`, `flights -> by_carrier`), or the source
-                  a materialization finding belongs to. Absent when a finding
-                  spans several, in which case the message names them.
+                  sits on (`by_carrier`, `flights -> by_carrier`), the source a
+                  materialization finding belongs to, or, for a dashboard
+                  finding, the dashboard's name or the `source.dimension` a
+                  `# drill` is declared on. Absent when a finding sits on none
+                  of those, either because it spans several, in which case the
+                  message names them, or because it is about the lint itself
+                  rather than about any one dashboard.
               message:
                 type: string
                 description: A description of the problem.
@@ -2925,9 +3090,21 @@ components:
                   - error
                   - warn
                 description: >-
-                  Finding severity. Currently only `error`-severity render
-                  findings are surfaced here; lower-severity findings remain on
-                  the query-time `renderLogs` surface.
+                  Finding severity. Render findings are surfaced here only at
+                  `error` severity; lower-severity render findings remain on the
+                  query-time `renderLogs` surface. Materialization and dashboard
+                  findings use both: `error` for something that cannot work as
+                  written, such as a tile naming a view the source does not
+                  have, and `warn` for something that works but not as the
+                  author probably intended, such as a dashboard held back by
+                  curation. The two findings about Publisher rather than about
+                  the package split across both: a file that carries an artifact
+                  tag and could not be read is `error`, because the dashboard it
+                  should have produced does not exist, and a lint that stopped
+                  early is `warn`, because the lint failing is not itself a
+                  defect in the package. That `warn` does NOT mean the package is
+                  free of `error`-severity findings, since the ones the lint
+                  never reached are exactly what it cannot report.
         queryableSources:
           type: string
           enum:
@@ -3175,19 +3352,196 @@ components:
       type: object
       description: Malloy notebook metadata and status information
       properties:
-        resource:
+        environmentName:
           type: string
-          description: Resource path to the notebook
+          description: Name of the environment containing this notebook
         packageName:
           type: string
           description: Name of the package containing this notebook
         path:
           type: string
           description: Relative path to the notebook file within its package directory
+        title:
+          type: string
+          description:
+            Human title, resolved from the notebook's own `## title="…"`, then
+            its `#"` doc comment, then its first markdown heading. Absent when
+            none of those resolve, leaving the caller to show the path.
+        description:
+          type: string
+          description: The notebook's `#"` doc comment, when it has one
         error:
           type: string
           description: Error message if the notebook failed to compile or load
+    Dashboard:
+      type: object
+      description: |
+        A dashboard within a Malloy package: a self-contained `.malloy` file in
+        the package's `dashboards/` directory carrying an `# artifact` (or
+        model-level `## artifact`) annotation. The list entry; see
+        DashboardManifest for the detail a viewer needs to render one.
+      properties:
+        resource:
+          type: string
+          description: Resource path to the dashboard
+        packageName:
+          type: string
+          description: Name of the package containing this dashboard
+        name:
+          type: string
+          description:
+            The dashboard's slug — its filename basename. Addresses it in a URL
+            and as a `# drill` target.
+        path:
+          type: string
+          description:
+            Relative path to the dashboard file within its package directory
+            (`dashboards/<name>.malloy`)
+        title:
+          type: string
+          description:
+            Human title from the artifact tag, falling back to the file's `#"`
+            doc comment and then to the slug
+        description:
+          type: string
+          description: The file's `#"` doc comment, when it has one
+        error:
+          type: string
+          description: Error message if the dashboard file failed to compile
+    DashboardManifest:
+      type: object
+      description: |
+        Everything a viewer needs to render one dashboard: the artifact tag's
+        declarations plus the control contract derived from the givens its query
+        references. Running needs no dashboard-specific endpoint — the query,
+        each composite tile, and each control's suggest query all run through
+        the ordinary model query endpoint with `givens`.
+      properties:
+        resource:
+          type: string
+          description: Resource path to the dashboard
+        packageName:
+          type: string
+          description: Name of the package containing this dashboard
+        name:
+          type: string
+          description:
+            The dashboard's slug — its filename basename. Addresses it in a URL
+            and as a `# drill` target.
+        path:
+          type: string
+          description: |
+            Relative path to the dashboard file within its package directory
+            (`dashboards/<name>.malloy`). This is also the model to POST to:
+            `query`, each tile, and each control's suggest query all run through
+            `POST /environments/{environmentName}/packages/{packageName}/models/{path}/query`
+            with `givens`, which is why there is no dashboard-specific run
+            endpoint.
+        title:
+          type: string
+          description:
+            Human title from the artifact tag, falling back to the file's `#"`
+            doc comment and then to the slug
+        description:
+          type: string
+          description: The file's `#"` doc comment, when it has one
+        error:
+          type: string
+          description: Error message if the dashboard file failed to compile
+        query:
+          type: string
+          description: >-
+            Name of the tagged query to run. Present for the single-query form
+            only; a composite dashboard carries `tiles` instead. A NAME rather
+            than an expression, so it goes in the `queryName` field of a
+            `POST …/models/{path}/query` body. A tile's `query` is the other
+            shape and is not interchangeable with this one; see
+            `DashboardTile.query`.
+        tiles:
+          type: array
+          description:
+            Tiles of a composite dashboard, run separately and combined into one
+            grid. Present for the composite form only.
+          items:
+            $ref: "#/components/schemas/DashboardTile"
+        dashboardColumns:
+          type: integer
+          description:
+            Grid width — from the `# dashboard {columns=N}` render tag, or
+            `dashboard_columns=N` on a composite artifact tag
+        startingGivens:
+          allOf:
+            - $ref: "#/components/schemas/EncodedGivenValues"
+          description:
+            Per-dashboard starting values for controls, from the artifact tag.
+            URL parameters override these, which is why the two share a shape.
+        autorun:
+          type: boolean
+          description:
+            False batches control changes behind an Apply button instead of
+            re-running on every change. Defaults to true.
+        givens:
+          type: array
+          description: |
+            The control row. Normally one entry per given the dashboard runs
+            with, which is what its `query` references on the single-query form
+            and the union over `tiles` on a composite, and which the entry file
+            can bind. A composite widens it to
+            every given the entry file surfaces when any tile is one discovery
+            cannot resolve, because that tile's givens are otherwise absent from
+            the row it filters by; see `DashboardTile.givenNames`. So an entry
+            here is always bindable, but on a widened row it is not necessarily
+            referenced by any tile. A given reachable only
+            through an import chain the entry file does not import itself
+            cannot be bound at query time, so no control is offered for it and
+            it stays at its default; that case is reported in the package's
+            `warnings` rather than represented here by an unusable entry. Plain
+            `Given`s, because the presentation a control takes is declared on
+            the given itself, so a dashboard and a notebook render the same
+            control for the same given, `#(description=…)` helper text
+            included.
+            ONE DELIBERATE DIVERGENCE from `Given` as the model surface sends
+            it: `default` here is the value the QUERY ENDPOINT takes, not the
+            Malloy source literal. A `filter<…>` given declared `f'West'`
+            publishes `West`. As the literal it could not be used as a default
+            at all, since sending it back verbatim matches zero rows silently,
+            with no error to search for. Only filter-typed givens are unwrapped,
+            so a plain string default that merely reads like `f'x'` is
+            untouched. `startingGivens` uses the same shape for the same reason.
+          items:
+            $ref: "#/components/schemas/Given"
+    DashboardTile:
+      type: object
+      description: One tile of a composite dashboard
+      properties:
+        query:
+          type: string
+          description: >-
+            The run expression exactly as written in `tiles=[…]`, for example
+            "orders -> by_month". An EXPRESSION rather than a name, so it goes in
+            the `query` field of a `POST …/models/{path}/query` body, prefixed
+            with `run:`. Sending it in `queryName`, the field
+            `DashboardManifest.query` takes, is rejected.
+        givenNames:
+          type: array
+          items:
+            type: string
+          description: |
+            Names of the givens this tile references. This is a scoping hint,
+            not a binding constraint: it tells a caller which tiles a changed
+            control actually needs to re-run. Running a tile with the
+            dashboard's whole control row also works, because an unreferenced
+            given is ignored. Absent when the tile expression is not one
+            discovery can resolve, a refinement or a multi-stage pipeline for
+            instance, in which case send the whole control row. One such tile
+            widens `DashboardManifest.givens` to every given the entry file
+            surfaces, rather than the union over the resolvable tiles, so that
+            the row actually contains the givens that tile filters by.
     DataApp:
       type: object
       description:
@@ -3259,6 +3613,14 @@ components:
             Starting values for the notebook's controls, declared at its file
             level. URL parameters override these, which is why the two share a
             shape. Omitted when the notebook declares none.
+        autorun:
+          type: boolean
+          description:
+            False batches control changes behind an Apply button instead of
+            re-running on every change. Defaults to true. The same flag, with
+            the same default, that `DashboardManifest.autorun` carries, so a
+            notebook's `## autorun=false` and a dashboard's
+            `# artifact { autorun=false }` arrive identically.
         sources:
           type: array
           description: Sources defined in the notebook's model
@@ -3391,12 +3753,16 @@ components:
         that survives a URL), and a bare list of names is spelled `givenNames`.
         It also carries how the given should be presented as an input control
-        (`label`, `control`, `rangeMin`, `rangeMax`, `suggest`), derived from
-        the declaration's own tags. That contract belongs to the given rather
-        than to any one surface, which is what lets a notebook and an SDK host
-        render the same control without restating it. Those five fields describe
-        the contract a renderer implements; no endpoint populates them yet, so
-        they are absent from every response today.
+        (`label`, `description`, `control`, `rangeMin`, `rangeMax`, `suggest`),
+        derived from the declaration's own tags. That contract belongs to the
+        given rather than to any one surface, which is what lets a notebook and
+        an SDK host render the same control without restating it. Each of those
+        six is present only when the declaration carries the tag it reads, so a
+        given tagged with none of them carries none of them. A tag whose value is
+        not one this contract accepts is dropped the same way rather than
+        reported, so an unrecognized `control`, or a `rangeMin`/`rangeMax` that is
+        not a number, is absent here and indistinguishable from never having been
+        written.
       properties:
         name:
           type: string
@@ -3420,6 +3786,15 @@ components:
         label:
           type: string
           description: Display label from the declaration's `# label=` tag
+        description:
+          type: string
+          description:
+            Helper text from the declaration's `# description=` tag. Distinct
+            from the older `#(description="…")` annotation, which is not derived
+            into this field and instead stays on `annotations` for the client
+            that already parses it. The tag form is also the one that compiles
+            without a `malformed-route` warning, because Malloy reads an
+            annotation's route up to the first whitespace.
         control:
           type: string
           enum:
@@ -3487,10 +3862,13 @@ components:
         The role it names: a surface's URL parameters and the starting values a
         document declares share this shape, so the two can merge and then be
-        decoded once against the declarations and sent as `GivenValues`. No
-        endpoint returns it yet. `RawNotebook.startingGivens` is the first field
-        typed as it, and nothing populates that field so far, so today this
-        schema documents the contract rather than describing live traffic. The
+        decoded once against the declarations and sent as `GivenValues`.
+        `RawNotebook.startingGivens` and `DashboardManifest.startingGivens` are
+        both typed as it and both populated, so this schema now describes live
+        traffic rather than only the contract. A `filter<…>` value is unwrapped
+        to its body and every other type is published as declared, keyed on the
+        declared type, so a plain string default that reads like `f'x'` survives
+        untouched. The
         `givens` query parameter is not an instance of it: that carries a
         JSON-encoded `GivenValues`, with values typed rather than stringified.
       additionalProperties:
@@ -5423,10 +5801,35 @@ components:
       properties:
         connectionName:
           type: string
-          description: With `physicalTableName`, the table the boundary belongs to.
+          description: >-
+            The connection whose SQL computes the table's rows. With
+            `physicalTableName` — and `storageDestinationName`, when the table is
+            in a storage destination — the table the boundary belongs to.
         physicalTableName:
           type: string
           description: The table's logical (unquoted) name, as the manifest reports it.
+        storageDestinationName:
+          type: string
+          description: >-
+            The storage destination the table lives in, when the source was
+            materialized into one — an entry in `storageDestinations`, NOT a
+            connection, exactly as on `ManifestEntry`. Absent means the table
+            lives in `connectionName`'s own warehouse.
+            Part of the table's IDENTITY, not a description of it, so it must be
+            returned verbatim like every other field here. A source keeps both its
+            physical name and its content address when `storage=` is added or
+            removed (an annotation enters neither), so without this field a
+            boundary measured on the stored table is indistinguishable from one
+            measured on a colocated table of the same name — and a delta computed
+            from the wrong one can skip rows.
+            A caller that has never recorded this field may omit it. An entry that
+            omits it for a source this run materializes into a destination
+            describes a different table, so that source SEEDS rather than being
+            rejected: the entry is stale, not wrong, and a seed is always correct.
+            An entry that names a DIFFERENT destination than the run instructs is
+            a caller error and is rejected like any other mismatched entry.
         coveredThrough:
           type: string
           description: >-
@@ -5665,14 +6068,24 @@ components:
             reach its own job records also reports null; that case is counted by
             `publisher_storage_build_attribution_skipped_total`.
-            An incremental delta reports null because its statements do not run
-            through a single call whose result reaches here. A chained `storage=`
-            build reports null because it read its parent's already-materialized
-            table and touched no warehouse at all. A POSTGRES source reports null
-            on every path: the label that makes a read reportable is BigQuery's,
-            and Postgres has no per-statement tag to carry one. And a bag whose
-            every property is unusable as a BigQuery label key renders no label,
-            so such a read is issued the untagged way and reports null too.
+            A COLOCATED incremental delta reports null because its statements do
+            not run through a single call whose result reaches here. A delta
+            into a `storage=` destination reports whatever its own bounded read
+            reported: that read is issued through the same call a full build's
+            is, so a tagged one is costed and an untagged one is not. A
+            SNOWFLAKE source reports null on a delta even though its full build
+            reports a figure — Snowflake does not return one with the read, so
+            the full build looks it up afterwards by matching the statement
+            text, and a delta's text is the bounded, projected wrapper rather
+            than the build SQL that lookup keys on. Summing this field across
+            refreshes therefore understates a Snowflake source; it does not mean
+            those reads were free. A chained `storage=` build reports null
+            because it read its parent's already-materialized table and touched
+            no warehouse at all. A POSTGRES source reports null on every path:
+            the label that makes a read reportable is BigQuery's, and Postgres
+            has no per-statement tag to carry one. And a bag whose every
+            property is unusable as a BigQuery label key renders no label, so
+            such a read is issued the untagged way and reports null too.
         dataAsOf:
           type: string
           format: date-time
@@ -5721,7 +6134,7 @@ components:
             Present exactly when the source is refreshed incrementally, so
             absent means only that it is not: a source declaring
             `refresh="full"`, or one whose declaration the delta path cannot act
-            on at all (an unsupported dialect, `storage=`), which the publish
+            on at all (an unsupported source dialect), which the publish
             gate rejects anyway.
   parameters:

package/dist/app/assets/{EnvironmentPage-DrTRtRHz.js → EnvironmentPage-CiuWaYTk.js} RENAMED Viewed

	@@ -1 +1 @@
1	- import{$ as r,H as t,j as e,a1 as i,aa as o}from"./index-~~BwoU1Ko8~~.js";function m(){const s=r(),{environmentName:n}=t();if(n){const a=i({environmentName:n});return e.jsx(o,{onSelectPackage:s,resourceUri:a})}else return e.jsx("div",{children:e.jsx("h2",{children:"Missing environment name"})})}export{m as default};
1	+ import{C as r,J as t,j as e,a3 as i,ad as o}from"./index-DP4bilgp.js";function m(){const s=r(),{environmentName:n}=t();if(n){const a=i({environmentName:n});return e.jsx(o,{onSelectPackage:s,resourceUri:a})}else return e.jsx("div",{children:e.jsx("h2",{children:"Missing environment name"})})}export{m as default};

package/dist/app/assets/HomePage-ZXsmEAjw.js ADDED Viewed

	@@ -0,0 +1 @@
1	+ import{C as t,j as o,g as a}from"./index-DP4bilgp.js";function s(){const n=t();return o.jsx(a,{onClickEnvironment:n})}export{s as default};

package/dist/app/assets/{LightMode-4Y7DEWAD.js → LightMode-10iLdX5H.js} RENAMED Viewed

	@@ -1 +1 @@
1	- import{c,j as s}from"./index-~~BwoU1Ko8~~.js";const t=c(s.jsx("path",{d:"M12 3c-4.97 0-9 4.03-9 9s4.03 9 9 9 9-4.03 9-9c0-.46-.04-.92-.1-1.36-.98 1.37-2.58 2.26-4.4 2.26-2.98 0-5.4-2.42-5.4-5.4 0-1.81.89-3.42 2.26-4.4-.44-.06-.9-.1-1.36-.1"})),a=c(s.jsx("path",{d:"M12 7c-2.76 0-5 2.24-5 5s2.24 5 5 5 5-2.24 5-5-2.24-5-5-5M2 13h2c.55 0 1-.45 1-1s-.45-1-1-1H2c-.55 0-1 .45-1 1s.45 1 1 1m18 0h2c.55 0 1-.45 1-1s-.45-1-1-1h-2c-.55 0-1 .45-1 1s.45 1 1 1M11 2v2c0 .55.45 1 1 1s1-.45 1-1V2c0-.55-.45-1-1-1s-1 .45-1 1m0 18v2c0 .55.45 1 1 1s1-.45 1-1v-2c0-.55-.45-1-1-1s-1 .45-1 1M5.99 4.58c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0s.39-1.03 0-1.41zm12.37 12.37c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0 .39-.39.39-1.03 0-1.41zm1.06-10.96c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0zM7.05 18.36c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0z"}));export{t as D,a as L};
1	+ import{c,j as s}from"./index-DP4bilgp.js";const t=c(s.jsx("path",{d:"M12 3c-4.97 0-9 4.03-9 9s4.03 9 9 9 9-4.03 9-9c0-.46-.04-.92-.1-1.36-.98 1.37-2.58 2.26-4.4 2.26-2.98 0-5.4-2.42-5.4-5.4 0-1.81.89-3.42 2.26-4.4-.44-.06-.9-.1-1.36-.1"})),a=c(s.jsx("path",{d:"M12 7c-2.76 0-5 2.24-5 5s2.24 5 5 5 5-2.24 5-5-2.24-5-5-5M2 13h2c.55 0 1-.45 1-1s-.45-1-1-1H2c-.55 0-1 .45-1 1s.45 1 1 1m18 0h2c.55 0 1-.45 1-1s-.45-1-1-1h-2c-.55 0-1 .45-1 1s.45 1 1 1M11 2v2c0 .55.45 1 1 1s1-.45 1-1V2c0-.55-.45-1-1-1s-1 .45-1 1m0 18v2c0 .55.45 1 1 1s1-.45 1-1v-2c0-.55-.45-1-1-1s-1 .45-1 1M5.99 4.58c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0s.39-1.03 0-1.41zm12.37 12.37c-.39-.39-1.03-.39-1.41 0-.39.39-.39 1.03 0 1.41l1.06 1.06c.39.39 1.03.39 1.41 0 .39-.39.39-1.03 0-1.41zm1.06-10.96c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0zM7.05 18.36c.39-.39.39-1.03 0-1.41-.39-.39-1.03-.39-1.41 0l-1.06 1.06c-.39.39-.39 1.03 0 1.41s1.03.39 1.41 0z"}));export{t as D,a as L};