@uniweb/projections 0.5.1 → 0.5.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/projections",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Projections of a Uniweb site's content — agent index, per-page markdown, search index. Pure JS, runs anywhere.",
   "type": "module",
   "exports": {
@@ -31,8 +31,8 @@
     "node": ">=20.19"
   },
   "dependencies": {
-    "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/core": "^0.13.1"
+    "@uniweb/core": "^0.14.0",
+    "@uniweb/content-writer": "^0.3.4"
   },
   "devDependencies": {
     "vitest": "^4.1.7",

package/src/search/generate.js

@@ -85,13 +85,13 @@ export function generateSearchIndex(siteContent, options = {}) {
  * describe *where the index lives* — only whether it serves queries.
  *
  * @param {Object} pagesIndex - Result of {@link generateSearchIndex}
- * @param {Object[]} [collectionIndexes] - Results of `generateRecordSearchIndex`
+ * @param {Object[]} [recordIndexes] - Results of `generateRecordSearchIndex`
  * @returns {Object} One index carrying every entry
  */
-export function mergeSearchIndexes(pagesIndex, collectionIndexes = []) {
+export function mergeSearchIndexes(pagesIndex, recordIndexes = []) {
   const entries = [
     ...(pagesIndex?.entries || []),
-    ...collectionIndexes.flatMap(index => index?.entries || [])
+    ...recordIndexes.flatMap(index => index?.entries || [])
   ]
 
   return {

package/src/search/records.js

@@ -29,8 +29,8 @@ function composeRoute(configRoute, slug) {
 
 /**
  * @param {string} name - Collection name (e.g. "articles")
- * @param {Object} config - Collection config from site.yml (config.collections[name])
- * @param {Object[]|Object} collectionData - Parsed cascade JSON (`data/{name}.json`),
+ * @param {Object} config - Query config from the site payload (config.queries[name])
+ * @param {Object[]|Object} recordData - Parsed cascade JSON (`data/{name}.json`),
  *   which the build writes as a bare array. The `{ items: [...] }` envelope is
  *   accepted too, since a host fetching the collection from a backend may carry one.
  * @param {string} locale - Locale code (e.g. "en")
@@ -66,7 +66,7 @@ const DISPLAY_VALUE_MAX = 200
 /**
  * Search-index entries for one named group of records.
  *
- * ⛔ RENAMED from `generateCollectionIndex` — 2026-08-27, and the old name was
+ * ⛔ RENAMED from `generateRecordIndex` — 2026-08-27, and the old name was
  * wrong in two ways that mattered.
  *
  * 1. **"Collection" is FRAMEWORK'S build concept** — a named set our build
@@ -86,7 +86,7 @@ const DISPLAY_VALUE_MAX = 200
  * being discussed cost one coordinated change; leaving it would have made the
  * entry the last place `collection` survived as a lane-crossing word.
  */
-export function generateRecordSearchIndex(name, config, collectionData, locale) {
+export function generateRecordSearchIndex(name, config, recordData, locale) {
   // ⛔ NO DEFAULT FIELD LIST. This was `|| ['title']` — a claim about someone
   // else's schema, and wrong for any collection without a `title` (a `people`
   // collection has `name`, a `products` one has `label`). The failure was
@@ -99,9 +99,9 @@ export function generateRecordSearchIndex(name, config, collectionData, locale)
   // has told us something we could not otherwise know.
   const declaredFields = Array.isArray(config.search?.fields) ? config.search.fields : null
   const weight = config.search?.weight ?? 0.7
-  const items = Array.isArray(collectionData)
-    ? collectionData
-    : collectionData?.items || []
+  const items = Array.isArray(recordData)
+    ? recordData
+    : recordData?.items || []
 
   const entries = items.map(item => {
     const fields = declaredFields ?? searchableKeys(item)