@malloydata/render 0.0.380 → 0.0.381

package/DEVELOPING.md

@@ -21,16 +21,21 @@ $ npm run --prefix packages/malloy-render storybook-windows
 
 Then navigate to the URL provided. In this storybook, you can navigate between different stories that render Malloy queries from the Malloy source code.
 
-### Tips
+### Iteration rules
 
-This storybook does not hot reload, so you need to reload the page when:
+Storybook does not use hot module replacement (HMR), but the Vite dev server stays running while you work. Most changes are picked up by a browser page reload; only boot-time artifacts require restarting Storybook.
 
-- you make changes to malloy-render source code
-- you add a new story
+| You change… | What you do |
+|---|---|
+| `.ts` / `.tsx` / `.css` in `src/` | Reload the browser page — Vite serves source directly, so changes are picked up on refresh |
+| A `.stories.malloy` file | Restart Storybook — the story indexer runs once at boot |
+| `.storybook/` config or `registered_data.json` | Restart Storybook |
+| A file in `src/stories/static/data/` | Reload the browser page |
+| Anything in `packages/malloy/src/` (Malloy core) | Restart Storybook |
 
-If you make changes to the malloy core package, you need to relaunch the storybook.
+You do **not** need to run `npm run build` as part of normal iteration. `npm run build` produces the published library bundles (`dist/module/index.umd.js`, `index.mjs`), which Storybook does not consume — Storybook reads source directly via Vite.
 
-It is fairly common for Malloy compilation to randomly fail when opening the storybook. A simple reload of the page fixes the problem.
+It is fairly common for Malloy compilation to randomly fail when first opening Storybook. A simple page reload fixes it.
 
 ## Adding new stories for viewing the renderer
 

package/README.md

@@ -56,4 +56,5 @@ The Malloy Renderer supports a plugin system for creating custom visualizations.
 
 # Developing
 
-See the [Developing README](./DEVELOPING.md)
+- [DEVELOPING.md](./DEVELOPING.md) — how to run Storybook, add stories, and debug renderers locally
+- [CONTEXT.md](./CONTEXT.md) — architectural overview for contributors and AI agents

package/dist/module/api/plugin-types.d.ts

@@ -21,12 +21,6 @@ interface BaseRenderPluginInstance<TMetadata = unknown> {
     processData?(field: NestField, cell: NestCell): void;
     beforeRender?(metadata: RenderMetadata, options: GetResultMetadataOptions): void;
     getStyleOverrides?(): Record<string, string>;
-    /**
-     * Legacy compatibility for plugins that still declare self-owned paths
-     * from the instance. New code should use factory.getValidationSpec().
-     * @deprecated Use RenderPluginFactory.getValidationSpec() instead.
-     */
-    getDeclaredTagPaths?(): string[][];
 }
 export interface SolidJSRenderPluginInstance<TMetadata = unknown> extends BaseRenderPluginInstance<TMetadata> {
     readonly renderMode: 'solidjs';

package/dist/module/component/chart/chart-layout-settings.d.ts

@@ -1,7 +1,7 @@
-import { Tag } from '@malloydata/malloy-tag';
 import { AlignValue, TextBaselineValue, Config, FontWeightValue } from 'vega';
 import { Field, NestField } from '../../data_tree';
 import { RenderMetadata } from '../render-result-metadata';
+import { ChartSizeConfig } from './resolve-chart-display';
 type XAxisSettings = {
     labelAngle: number;
     labelAlign?: AlignValue;
@@ -66,7 +66,8 @@ export type ChartLayoutSettings = {
     totalHeight: number;
     isSpark: boolean;
 };
-export declare function getChartLayoutSettings(field: NestField, chartTag: Tag, options: {
+export declare function getChartLayoutSettings(field: NestField, options: {
+    size: ChartSizeConfig;
     metadata: RenderMetadata;
     xField?: Field;
     yField?: Field;

package/dist/module/component/chart/chart-v2.d.ts

@@ -10,9 +10,8 @@ export type ChartV2Props = {
     plotHeight: number;
     totalWidth: number;
     totalHeight: number;
-    chartTag?: {
-        text?: (key: string) => string | undefined;
-    };
+    title?: string;
+    subtitle?: string;
     getTooltipData?: (item: Item, view: View) => ChartTooltipEntry | null;
     isDataLimited?: boolean;
     dataLimitMessage?: string;

package/dist/module/component/chart/resolve-chart-display.d.ts

@@ -0,0 +1,21 @@
+import { Tag } from '@malloydata/malloy-tag';
+import { NestField } from '../../data_tree';
+export interface ChartSizeConfig {
+    width?: number;
+    height?: number;
+    preset?: string;
+}
+export interface ChartDisplayConfig {
+    title?: string;
+    subtitle?: string;
+    size: ChartSizeConfig;
+}
+/**
+ * Setup-time resolver for chart display tags (title, subtitle, size).
+ *
+ * Reads the `viz.title`, `viz.subtitle`, `viz.size.*` properties plus the
+ * legacy top-level `size.*` fallback. Called from each chart plugin's
+ * `create()` so the reads happen during `setResult()` — no tag access
+ * needed at render time for these paths.
+ */
+export declare function resolveChartDisplayConfig(field: NestField, chartTag: Tag): ChartDisplayConfig;

package/dist/module/component/types.d.ts

@@ -1,4 +1,3 @@
-import { Tag } from '@malloydata/malloy-tag';
 import { Item, Spec, View } from 'vega';
 import { JSX } from 'solid-js';
 import { Cell, DrillEntry, Field, RecordCell, RepeatedRecordCell } from '../data_tree';
@@ -28,7 +27,8 @@ export type VegaChartProps = {
     totalWidth: number;
     totalHeight: number;
     chartType: string;
-    chartTag: Tag;
+    title?: string;
+    subtitle?: string;
     mapMalloyDataToChartData: MalloyDataToChartDataHandler;
     getTooltipData?: (item: Item, view: View) => ChartTooltipEntry | null;
 };
@@ -67,6 +67,9 @@ export type Channel = {
     type: ScaleType | null;
     independent: boolean | 'auto';
 };
+export type XChannel = Channel & {
+    limit: number | 'auto';
+};
 export type YChannel = {
     fields: string[];
     type: ScaleType | null;