@abeedoo/radish-schemas 1.9.0 → 1.10.0

package/index.js

@@ -31,7 +31,7 @@ export {
  * @property {string} minCliVersion - Minimum radish-cli version compatible with this package
  */
 export const VERSIONING = {
-  packageVersion: '1.9.0',
+  packageVersion: '1.10.0',
   currentSpecVersion: 1,
   supportedSpecVersions: [1],
   minCliVersion: '0.1.0'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@abeedoo/radish-schemas",
-  "version": "1.9.0",
+  "version": "1.10.0",
   "description": "Shared JSON schemas, validators, and prompts for Radish CLI ecosystem",
   "main": "index.js",
   "type": "module",

package/prompts/radish-types-generation.md

@@ -188,6 +188,21 @@ The following entities are already provided by the system. DO NOT recreate them
     - **sync**: `inline` (immediate) or `background` (via jobs)
     - **vector**: Enable vector/embedding search with `sourceFields` to generate embeddings from
     - **searchable**: Each entry is either a plain field name or `{ "field": "name", "stem": true }`. Stemming reduces terms to their word stems at index time (`computers` → `computer`), so a plural query matches singular text as an exact match rather than relying on typo correction. Set `stem: true` only on prose fields (name, description, summary, body). Never stem identifiers (`sku`, `slug`, `code`), brand or category values, anything listed under `filterable`/`facetable`, or non-string fields — stemming a facet value breaks the filter that reads it.
+    - **configureBy**: `"rows"` marks an entity whose *records* are vocabulary for other entities' search indexes — each row (or group of rows) becomes a candidate field in the consuming entity's search configuration. Use it for entities that define terminology rather than content: `Attribute`, `Term`, `Tag`, `Taxonomy`. The system discovers code/label fields and grouping refs from the entity's own field definitions, so no extra configuration is needed. A vocabulary entity that is not itself searchable needs only `"search": { "configureBy": "rows" }`; combine with `"enabled": true` when the entity should also have its own index:
+      ```json
+      "Term": {
+        "plural": "terms",
+        "search": {
+          "enabled": true,
+          "configureBy": "rows",
+          "fields": {
+            "searchable": [{ "field": "name", "stem": true }, "slug"],
+            "filterable": ["taxonomyId"]
+          }
+        },
+        "fields": { ... }
+      }
+      ```
 
 13. **Expiration / TTL** (optional): For entities whose records should be purged automatically (sessions, tokens, logs, temporary uploads), use the entity-level `ttl` shorthand:
     ```json

package/schemas/types.schema.json

@@ -90,8 +90,7 @@
             },
             "search": {
               "type": "object",
-              "description": "Search index configuration for this entity. Generates search adapters and typed search index classes.",
-              "required": ["enabled"],
+              "description": "Search index configuration for this entity. Generates search adapters and typed search index classes. An entity with configureBy: 'rows' declares its records as vocabulary for other entities' indexes.",
               "additionalProperties": false,
               "properties": {
                 "enabled": {
@@ -173,6 +172,11 @@
                       "description": "Fields to generate embeddings from"
                     }
                   }
+                },
+                "configureBy": {
+                  "type": "string",
+                  "enum": ["rows"],
+                  "description": "How this entity participates in search configuration. 'rows' means this entity's records are vocabulary for other entities' indexes — each row (or group of rows) becomes a candidate field in the consumer's search config UI. The system discovers code/label fields and grouping refs from the entity's own field definitions. Combinable with enabled: true for entities that are both searchable and vocabulary sources (e.g. Term)."
                 }
               }
             },