dataface 0.1.6.dev183__py3-none-any.whl → 0.1.6.dev321__py3-none-any.whl

dataface/DATAFACE_SYNTAX.md

@@ -797,58 +797,6 @@ Dataface composes charts in three ways:
 
 Non-goals (not part of the authored chart surface): Vega-Lite `encoding`, `mark`, `spec`, `config`, `transform`, `params`, `resolve`, `hconcat`, `vconcat`, `concat`, `repeat`. These keys are rejected at compile time. Use the typed channels (`x`, `y`, `color`, …) and `style:` instead; use the layout primitives for visual composition.
 
-### Custom chart plugins
-
-Project-local chart types can extend the engine. Drop a `chart_types/<name>.yml` file next to the face files and reference the name in `type:`.
-
-```yaml
-# chart_types/funnel.yml
-name: funnel
-description: Funnel chart for conversion visualization
-mark: bar                              # Underlying Vega-Lite mark
-fields:
-  stage:
-    required: true
-    description: Stage field
-  value:
-    required: true
-    description: Value field
-encoding_overrides:
-  y:
-    type: nominal
-    sort: null
-  x:
-    type: quantitative
-mark_properties:
-  cornerRadius: 4
-```
-
-Then in a face:
-
-```yaml-schema
-charts:
-  conversion_funnel:
-    query: stages
-    type: funnel                       # The plugin name; no `custom:` prefix
-    # The plugin's required fields must be present in the data.
-```
-
-Plugin file fields:
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| `name` | yes | Lowercase identifier (regex `[a-z][a-z0-9_]*`) — must not shadow a built-in |
-| `mark` | yes | Vega-Lite mark name (must be a valid VL mark) |
-| `description` | no | Used in docs and AI prompts |
-| `fields` | no | `{<name>: {required: bool, description: string}}` |
-| `encoding_overrides` | no | Per-channel Vega-Lite encoding properties merged on top of standard mapping |
-| `mark_properties` | no | Extra properties merged into the mark dict |
-
-Constraints:
-- A plugin cannot shadow a built-in chart type name.
-- The `mark` value must be a valid Vega-Lite mark (validated at load time).
-- Unknown YAML keys in the plugin file are rejected — typos are caught up front.
-
 **See also:** `dft docs queries` (charts reference queries by name),
 `dft docs variables` (use `{{ var }}` in chart queries),
 `dft docs layout` (compose charts on the page),

dataface/agent_api/_init_templates/meta.yaml

@@ -0,0 +1,19 @@
+# Directory defaults for every face under faces/
+#
+# meta.yaml is a *partial face* — it uses the exact same authoring surface as a
+# face file (source, theme, queries, charts, style, variables), but without a
+# layout. Its keys are deep-merged as defaults beneath every face in this
+# directory and its subdirectories; each face overrides what it sets.
+#
+# A meta.yaml deeper in the tree layers on top of the ones above it, and a face
+# always wins over meta. Nested style keys merge (a face setting style.board.margin
+# keeps a meta-supplied style.board.width).
+#
+# Uncomment and edit to set project-wide defaults:
+#
+# theme: cream            # apply a built-in or custom theme to every dashboard
+# source: my_warehouse    # default data source for faces that don't name one
+#
+# style:
+#   board:
+#     width: 1000