astroidjs 0.12.1 → 0.13.0

package/src/components/justify.ts

@@ -4,9 +4,9 @@
 //
 // The layout every photo grid actually wants: images keep their aspect ratios,
 // each row is exactly as wide as the container, and rows land near a target
-// height. CSS can't express it — `grid` needs uniform tracks, and `columns`
+// height. CSS can't express it—`grid` needs uniform tracks, and `columns`
 // gives you a masonry *column* flow where reading order runs down instead of
-// across — so it's arithmetic, done once here rather than re-derived per site.
+// across—so it's arithmetic, done once here rather than re-derived per site.
 //
 // Pure and synchronous on purpose. It's called twice for the same gallery:
 // once during SSR with the aspect ratios the media library recorded, and again
@@ -28,14 +28,14 @@ export interface JustifyItem {
  * One image in a `<JustifiedGallery>`.
  *
  * Declared here rather than in the `.astro` component so consumers can import
- * the type from a plain module — an `.astro` file's non-`Props` exports are
+ * the type from a plain module—an `.astro` file's non-`Props` exports are
  * awkward to reach from TypeScript, and a scaffolded page shouldn't have to.
  */
 export interface GalleryItem {
   src: string;
   /**
    * Alternative text. Required, and `""` is a legitimate value for a purely
-   * decorative tile — what must not happen is the attribute going missing.
+   * decorative tile—what must not happen is the attribute going missing.
    */
   alt: string;
   /** Intrinsic dimensions, when the media library recorded them. Used for the
@@ -49,7 +49,7 @@ export interface GalleryItem {
 
 /** A laid-out item: its position in the input, at a concrete pixel size. */
 export interface JustifiedBox {
-  /** Index into the input array — the caller maps this back to its own data. */
+  /** Index into the input array—the caller maps this back to its own data. */
   index: number;
   width: number;
   height: number;
@@ -80,8 +80,8 @@ export interface JustifyOptions {
   lastRowSlack?: number;
 }
 
-/** Aspect used for an item whose real ratio isn't known yet (3:2 landscape —
- *  the most common photographic frame, so first paint is usually close). */
+/** Aspect used for an item whose real ratio isn't known yet (3:2 landscape—*
+  the most common photographic frame, so first paint is usually close). */
 export const DEFAULT_ASPECT = 1.5;
 
 /** Clamp a caller-supplied aspect into something layout-safe. A zero or NaN
@@ -97,7 +97,7 @@ function safeAspect(aspect: number): number {
  * The rule per row: with n items of total aspect A and n−1 gaps, the height
  * that makes the row exactly fill is `(containerWidth − gap·(n−1)) / A`. Adding
  * items only ever *lowers* that height, so items are appended until it drops to
- * `targetHeight` and the row closes — which is why rows come out near, but
+ * `targetHeight` and the row closes—which is why rows come out near, but
  * never exactly at, the target.
  *
  * ```ts
@@ -135,7 +135,7 @@ export function justifyRows(items: JustifyItem[], options: JustifyOptions): Just
       // Every box but the last takes its proportional share; the last takes
       // whatever is left, so the row's widths sum to `available` exactly and the
       // right edge stays flush. An un-stretched trailing row keeps natural
-      // widths instead — it isn't meant to reach the edge.
+      // widths instead—it isn't meant to reach the edge.
       const width =
         stretch && last
           ? available - used

package/src/components/media-meta.ts

@@ -4,8 +4,8 @@
 //
 // A section stores an image as a URL. The `alt` and `caption` an editor typed
 // live on the media ASSET, so rendering a page's images correctly means joining
-// every image field back to the media registry. Done naively — a query per
-// `<MediaSlot>` — a gallery section is thirty round-trips to D1 on every render.
+// every image field back to the media registry. Done naively—a query per
+// `<MediaSlot>`—a gallery section is thirty round-trips to D1 on every render.
 //
 // So the whole page is resolved in ONE bounded `IN (...)` lookup before anything
 // renders, and the result is threaded down as `mediaMeta`. This is the pattern
@@ -13,7 +13,7 @@
 //
 // The collection step is SCHEMA-DRIVEN: it walks the catalog looking for fields
 // of `type: "image"` rather than hardcoding field names. That's what keeps it
-// correct as sections are added — a new section with an image field is picked up
+// correct as sections are added—a new section with an image field is picked up
 // because it declared one, not because someone remembered to update a list here.
 //
 // Self-contained (ships as source): type-only imports, no astroid `src/*` reach.
@@ -26,7 +26,7 @@ import type { MediaMeta } from "./sections.js";
 const CHUNK = 100;
 
 /** Walk one item's declared fields, collecting the values of `image` ones.
- *  Recurses into `array` item fields — a gallery's images live there. */
+ *  Recurses into `array` item fields—a gallery's images live there. */
 function collectFrom(
   item: Record<string, unknown>,
   fields: Record<string, SectionField> | undefined,
@@ -41,7 +41,7 @@ function collectFrom(
       for (const row of value) {
         if (typeof row !== "object" || row === null || Array.isArray(row)) continue;
         // With a discriminator, an item's variant contributes extra fields on
-        // top of the shared set — an image declared only on the "image" variant
+        // top of the shared set—an image declared only on the "image" variant
         // of a blocks-style array would be missed otherwise.
         const sub = row as Record<string, unknown>;
         let itemFields = field.itemFields ?? {};
@@ -60,7 +60,7 @@ function collectFrom(
 /**
  * Every media URL a page's sections reference, deduplicated.
  *
- * Blocks are walked too, against the block catalog — a section's images and its
+ * Blocks are walked too, against the block catalog—a section's images and its
  * blocks' images are the same lookup, and splitting them would reintroduce the
  * per-section query this exists to avoid.
  */
@@ -96,7 +96,7 @@ export interface MediaMetaDatabase {
 /**
  * Turn a public media URL into its registry `key`.
  *
- * The public URL is `MEDIA_URL + "/" + key`, so this is prefix removal — but it
+ * The public URL is `MEDIA_URL + "/" + key`, so this is prefix removal—but it
  * has to tolerate an absolute URL too (a site whose media base is a full origin),
  * which is why it falls back to the pathname's last segment rather than assuming
  * the string starts with `mediaBase`.
@@ -105,7 +105,7 @@ export function mediaKeyFromUrl(url: string, mediaBase: string): string | null {
   if (!url) return null;
   const base = mediaBase.replace(/\/+$/, "");
   if (base && url.startsWith(`${base}/`)) return url.slice(base.length + 1);
-  // Absolute or unexpected shape — take the path's tail, which is the key for
+  // Absolute or unexpected shape—take the path's tail, which is the key for
   // every URL the media route produces.
   try {
     const path = url.startsWith("http") ? new URL(url).pathname : url;
@@ -122,7 +122,7 @@ export function mediaKeyFromUrl(url: string, mediaBase: string): string | null {
  * Returns `{}` on any failure rather than throwing: missing alt text degrades a
  * page, but a media table that isn't provisioned yet must not take the whole
  * render down with it. The caller's per-image `alt` (a usage-level override)
- * always wins over what comes back here — this is the ASSET-level fallback.
+ * always wins over what comes back here—this is the ASSET-level fallback.
  */
 export async function resolveSectionMedia(
   db: MediaMetaDatabase | undefined,
@@ -131,7 +131,7 @@ export async function resolveSectionMedia(
 ): Promise<MediaMeta> {
   if (!db || urls.length === 0) return {};
 
-  // key → the URL(s) that produced it, so results map back to what the sections
+  // key → the URLs that produced it, so results map back to what the sections
   // actually reference.
   const byKey = new Map<string, string[]>();
   for (const url of urls) {

package/src/components/sections/AboutIntro.astro

@@ -1,5 +1,5 @@
 ---
-// A portrait beside an introduction — the "about the maker" opener.
+// A portrait beside an introduction—the "about the maker" opener.
 import type { SectionRenderProps } from "../sections.js";
 import { colorwayClass, field, mediaAlt, setting } from "../sections.js";
 import Editable from "../Editable.astro";

package/src/components/sections/Contact.astro

@@ -1,5 +1,5 @@
 ---
-// Contact section — a heading + blurb + link to the contact route (the generated
+// Contact section—a heading + blurb + link to the contact route (the generated
 // worker's contact form lives at /contact).
 import type { SectionRenderProps } from "../sections.js";
 import { colorwayClass, field, setting } from "../sections.js";

package/src/components/sections/Cta.astro

@@ -1,5 +1,5 @@
 ---
-// Call-to-action band. Defaults to the brand colorway — a setting token, so an
+// Call-to-action band. Defaults to the brand colorway—a setting token, so an
 // editor can change it in the inspector without touching this file.
 import type { SectionRenderProps } from "../sections.js";
 import { alignClass, colorwayClass, field, setting } from "../sections.js";

package/src/components/sections/Faq.astro

@@ -3,7 +3,7 @@
 //
 // Native rather than a JS accordion on purpose: it is keyboard-accessible and
 // screen-reader-correct with no script, it works before hydration, and browser
-// find-in-page can open a collapsed answer — which a div-based accordion
+// find-in-page can open a collapsed answer—which a div-based accordion
 // silently breaks.
 import type { SectionRenderProps } from "../sections.js";
 import { colorwayClass, field, itemField, list, setting } from "../sections.js";

package/src/components/sections/FeatureGrid.astro

@@ -1,9 +1,9 @@
 ---
-// Feature-grid section — value-prop cards over an `array` field.
+// Feature-grid section—value-prop cards over an `array` field.
 //
 // The array is where `base` earns its keep. Each card's fields address
 // `<base>.items.<i>.<key>`, so the marker is built from the item's position
-// rather than a fixed slot name — which is why the schema can use a real
+// rather than a fixed slot name—which is why the schema can use a real
 // repeatable array instead of the `card1…card6` flattening sites fall back to.
 // The client's path parser is depth-agnostic (it splits on `.` and coerces
 // numeric segments), so this needs nothing new on the editor side.

package/src/components/sections/Hero.astro

@@ -39,7 +39,7 @@ const ctaHref = field(item, "ctaHref");
           {subheading}
         </Editable>
       )}
-      {/* The label is editable in place; the href is not — you can't point at a
+      {/* The label is editable in place; the href is not—you can't point at a
           URL, so it lives in the inspector (`inline: false` in the catalog). */}
       {ctaLabel && ctaHref && (
         <a class="btn btn-primary" href={ctaHref}>

package/src/components/sections/PricingTiers.astro

@@ -1,6 +1,6 @@
 ---
 // Pricing tiers. Each tier's feature list is a nested array, so a feature's
-// marker path is `<base>.items.<i>.features.<j>.text` — two levels of position,
+// marker path is `<base>.items.<i>.features.<j>.text`—two levels of position,
 // which the client's path parser handles because it splits on `.` and coerces
 // every numeric segment.
 import type { SectionRenderProps } from "../sections.js";

package/src/components/sections/ProductGrid.astro

@@ -4,7 +4,7 @@
 // Deliberately NOT a live catalog read. A section is stored content that an
 // editor curates; the commerce mirror has its own loader (`readCatalog`) with
 // its own freshness story. A site that wants the live catalog renders it in a
-// page, not through the page-builder — mixing the two would make a section's
+// page, not through the page-builder—mixing the two would make a section's
 // stored value and what it displays disagree, and the editor would be editing
 // something that isn't there.
 import type { SectionRenderProps } from "../sections.js";

package/src/components/sections/SplitImage.astro

@@ -1,6 +1,6 @@
 ---
 // Image beside copy. Which side the image sits on is a `_layout` token, so an
-// editor flips it from the inspector and Louise stores `"imageEnd"` — never a
+// editor flips it from the inspector and Louise stores `"imageEnd"`—never a
 // class name. The mapping from token to CSS is here, where it belongs.
 import type { SectionRenderProps } from "../sections.js";
 import { colorwayClass, field, mediaAlt, setting } from "../sections.js";

package/src/components/sections/Steps.astro

@@ -1,5 +1,5 @@
 ---
-// A numbered sequence — "how it works", a commission process, an onboarding
+// A numbered sequence—"how it works", a commission process, an onboarding
 // flow. The number is generated from position rather than stored, so reordering
 // steps in the inspector renumbers them with no content edit.
 import type { SectionRenderProps } from "../sections.js";

package/src/components/sections/Testimonial.astro

@@ -41,7 +41,7 @@ const image = field(item, "image");
         </Editable>
         {role && (
           <>
-            {attribution && <span aria-hidden="true"> — </span>}
+            {attribution && <span aria-hidden="true"> · </span>}
             <Editable as="span" base={base} field="role" edit={edit}>{role}</Editable>
           </>
         )}

package/src/components/sections.ts

@@ -5,8 +5,8 @@
 //
 // This file used to define a parallel universe: a `SectionProps` union
 // discriminated on `kind`, with `colorway`/`align` as component props. Louise's
-// actual model — the one the on-canvas editor and the write-time validator both
-// read — is different in every particular, and it is the one that wins:
+// actual model—the one the on-canvas editor and the write-time validator both
+// read—is different in every particular, and it is the one that wins:
 //
 //   • a section is a stored `SectionItem`: `{ _type, blocks?, _layout?,
 //     _settings?, ...fields }`. The discriminant is `_type`, not `kind`.
@@ -16,7 +16,7 @@
 //     or validated-but-uneditable.
 //   • presentation choices are `_settings` / `_layout` **tokens**. Louise stores
 //     the token; the site maps it to CSS. That's why COLORWAY_CLASS below stays
-//     — it is exactly the site-owned half of that contract — while `colorway`
+//: it is exactly the site-owned half of that contract—while `colorway`
 //     stops being a prop and becomes a stored setting.
 //
 // ADR 0005 §2 names this file's job outright: "<Section> reads `_layout` /
@@ -26,7 +26,7 @@
 //
 // Self-contained on purpose: this module ships as SOURCE (the `.astro` files
 // beside it import it directly), so it must not reach back into astroid's built
-// `src/*` — only siblings and external packages. The `louise-toolkit/content`
+// `src/*`—only siblings and external packages. The `louise-toolkit/content`
 // import is TYPE-ONLY, so it erases at build and never drags the validator (or
 // drizzle, which that entry pulls in) into a page bundle.
 
@@ -87,7 +87,7 @@ const tokenOptions = (map: Record<string, string>) =>
  *
  * These are closed token sets, declared as `select` (#272) so the inspector
  * renders a picker and an unknown token is rejected on write. They used to be
- * `text` with the valid values stuffed into `placeholder` — which meant a typo
+ * `text` with the valid values stuffed into `placeholder`—which meant a typo
  * wasn't a validation error at all, just a silent fallback to the default
  * inside `colorwayClass` at render time.
  */
@@ -97,7 +97,7 @@ export const SECTION_SETTINGS: Record<string, SectionField> = {
     label: "Colorway",
     inline: false,
     options: tokenOptions(COLORWAY_CLASS),
-    // An opaque hint — the schema layer doesn't know what a swatch looks like;
+    // An opaque hint—the schema layer doesn't know what a swatch looks like;
     // a renderer that doesn't support it just shows a normal picker.
     display: "swatch",
   },
@@ -113,8 +113,8 @@ export const SECTION_SETTINGS: Record<string, SectionField> = {
  * What every section render component receives.
  *
  * `base` is the whole point. It is this item's path within the page's `sections`
- * array — `"2"` for a top-level section, `"2.blocks.0"` for a block inside it —
- * and every marker the component stamps is built from it. Passing it down (rather
+ * array—`"2"` for a top-level section, `"2.blocks.0"` for a block inside it—and
+ * every marker the component stamps is built from it. Passing it down (rather
  * than having each component work out its own depth) is what lets the exact same
  * component render as a section or as a block, and what keeps `data-louise-node`
  * paths correct at any nesting depth.
@@ -126,8 +126,8 @@ export interface SectionRenderProps {
   base: string;
   /** Whether to stamp edit markers. Defaults to `Astro.locals.editMode`. */
   edit?: boolean;
-  /** Alt/caption resolved from the media registry, keyed by public URL —
-   *  looked up once for the whole page by `<Sections>`. */
+  /** Alt/caption resolved from the media registry, keyed by public URL—*
+    looked up once for the whole page by `<Sections>`. */
   mediaMeta?: MediaMeta;
 }
 
@@ -169,7 +169,7 @@ export function itemField(row: Record<string, unknown>, key: string): string | u
  *
  * The precedence is the whole reason `<Sections>` does its media lookup: a
  * per-usage `alt` on the section wins, because the same photo means something
- * different in a hero than in a thumbnail strip — but when there isn't one, the
+ * different in a hero than in a thumbnail strip—but when there isn't one, the
  * alt an editor typed once in the media library is used. That's what makes
  * fixing alt text a single edit that propagates everywhere the asset appears,
  * instead of a hunt through every page that embeds it.
@@ -188,7 +188,7 @@ export function mediaAlt(
 }
 
 /** Caption for an image, same precedence as {@link mediaAlt}. Undefined when
- *  there is none — a missing caption renders nothing, unlike a missing alt. */
+ *  there is none—a missing caption renders nothing, unlike a missing alt. */
 export function mediaCaption(
   mediaMeta: MediaMeta | undefined,
   src: string | undefined,
@@ -208,7 +208,7 @@ export function mediaCaption(
  * `satisfies` rather than a `: SectionCatalog` annotation, and it matters:
  * `SectionCatalog` is `Record<string, SectionDef>`, so annotating would widen
  * `keyof typeof` to `string` and throw away the literal keys. Those keys are
- * the project's whole section vocabulary — `SectionKind` is derived from them
+ * the project's whole section vocabulary—`SectionKind` is derived from them
  * (config.ts), `isRenderableSection` narrows to them, and `<Section>` indexes
  * its component map with them. Annotate this and all three silently degrade to
  * "any string", which is how the dispatcher lost its type safety once already.
@@ -221,7 +221,7 @@ export const astroidSectionCatalog = {
       heading: { type: "text", label: "Heading", validation: (r) => r.required().max(120) },
       subheading: { type: "textarea", label: "Subheading" },
       // A link URL is something you can't point at on the page, so it is not
-      // inline — it belongs in the inspector, which is what `inline: false` says.
+      // inline—it belongs in the inspector, which is what `inline: false` says.
       ctaLabel: { type: "text", label: "Button label" },
       ctaHref: { type: "text", label: "Button link", inline: false },
     },
@@ -367,7 +367,7 @@ export const astroidSectionCatalog = {
           name: { type: "text", label: "Name", validation: (r) => r.required() },
           price: { type: "text", label: "Price" },
           period: { type: "text", label: "Period (e.g. /mo)" },
-          // A list of strings isn't expressible — array items are objects — so
+          // A list of strings isn't expressible—array items are objects—so
           // each feature is a one-field row. That also leaves room to add an
           // `included` flag later without a data migration.
           features: {
@@ -424,7 +424,7 @@ export const astroidSectionCatalog = {
       heading: { type: "text", label: "Heading" },
       // Deliberately hand-authored rows rather than a live catalog read. A
       // section is stored content, and the commerce mirror is a separate
-      // concern with its own loader — a site that wants the live catalog renders
+      // concern with its own loader—a site that wants the live catalog renders
       // `readCatalog` in its own page, not through the page-builder.
       items: {
         type: "array",
@@ -472,7 +472,7 @@ export const astroidSectionCatalog = {
   },
 } satisfies SectionCatalog;
 
-/** The `_type`s with a shipped render component — derived from the catalog, so
+/** The `_type`s with a shipped render component—derived from the catalog, so
  *  it can't drift from what `<Section>` actually dispatches. A literal union,
  *  not `string`, because the catalog is declared with `satisfies`. */
 export type RenderableSectionType = keyof typeof astroidSectionCatalog;