@stapel/search-react 0.14.1 → 0.14.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +21 -0
- package/dist/headless/useFacetLabels.js +1 -1
- package/llms.txt +1 -1
- package/manifest.json +1 -1
- package/nav-manifest.json +1 -1
- package/package.json +2 -2
- package/src/analytics/generated/events.json +1 -1
- package/src/headless/useFacetLabels.ts +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,26 @@
|
|
|
1
1
|
# @stapel/search-react
|
|
2
2
|
|
|
3
|
+
## 0.14.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- The imported rule corpus and the vocabulary examples are source-neutral.
|
|
8
|
+
|
|
9
|
+
`test/fixtures/rules-corpus/imported/` replaces the directory named after the
|
|
10
|
+
external marketplace the corpus was imported from, and both files were
|
|
11
|
+
regenerated upstream (stapel-attributes 0.7.1) with a synthetic option
|
|
12
|
+
vocabulary and structural notes. The rewrite is injective per case, so the
|
|
13
|
+
TypeScript evaluator is still measured against exactly the same 3890 rules at
|
|
14
|
+
both polarities — 7780 frames, 15 730 feature-state expectations, the same
|
|
15
|
+
effect mix and the same shape gate. `scripts/gen-rules-corpus.mjs` copies the
|
|
16
|
+
`imported` set, and the `stapel-attributes` contract pin moves to v0.7.1.
|
|
17
|
+
|
|
18
|
+
Examples and demo data drop the source's name too: the worked vocabulary is
|
|
19
|
+
`phone-models` / `car-models` / `phone-catalog` across the attributes,
|
|
20
|
+
vocabularies, search and listings pairs. Comments, READMEs and changelog prose
|
|
21
|
+
say "an imported external catalogue" where they used to name the marketplace.
|
|
22
|
+
No runtime behaviour, exported API or wire shape changes.
|
|
23
|
+
|
|
3
24
|
## 0.14.1
|
|
4
25
|
|
|
5
26
|
### Patch Changes
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
* A live classified deployment's category schema types `vendor`, `model`,
|
|
8
8
|
* `memory_size` and `color_ref_select` as `ref_select`: their config carries
|
|
9
9
|
* no `options` table at all, only a POINTER —
|
|
10
|
-
* `{"optionsRef": {"level": "Vendor", "vocabulary": "
|
|
10
|
+
* `{"optionsRef": {"level": "Vendor", "vocabulary": "phone-catalog"}}`.
|
|
11
11
|
* The words live in the vocabulary the pointer names, which is a different
|
|
12
12
|
* service with a different client. So the two label sources this pair already
|
|
13
13
|
* has both come up empty: the answer's `facet_labels` because the deployed
|
package/llms.txt
CHANGED
package/manifest.json
CHANGED
package/nav-manifest.json
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@stapel/search-react",
|
|
3
|
-
"version": "0.14.
|
|
3
|
+
"version": "0.14.2",
|
|
4
4
|
"description": "Headless React pair for stapel-search: a typed query client, TanStack Query hooks, and a URL-first state codec that makes a search shareable by construction (filters, ranges, geo, sort and the keyset cursor all live in the query string). Drill-down facets rendered with their remaining counts and with the server's own honesty flags — approximate, skipped, degraded — never swallowed; keyset pagination with the window refusal named; DSA Art. 26 `promoted` marking carried into every card slot and the P2B Art. 5 ranking disclosure exposed as data. Zero visual opinion in the main entry; an opt-in /default subpath ships the antd skin, and /router binds the codec to react-router's useSearchParams.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -115,7 +115,7 @@
|
|
|
115
115
|
"size-limit": "^11.2.0",
|
|
116
116
|
"typescript": "^5.8.3",
|
|
117
117
|
"vitest": "^3.2.4",
|
|
118
|
-
"@stapel/attributes-react": "^0.8.
|
|
118
|
+
"@stapel/attributes-react": "^0.8.1",
|
|
119
119
|
"@stapel/core": "^0.22.0",
|
|
120
120
|
"@stapel/image": "^0.4.2",
|
|
121
121
|
"@stapel/showcase": "^0.3.0",
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
* A live classified deployment's category schema types `vendor`, `model`,
|
|
8
8
|
* `memory_size` and `color_ref_select` as `ref_select`: their config carries
|
|
9
9
|
* no `options` table at all, only a POINTER —
|
|
10
|
-
* `{"optionsRef": {"level": "Vendor", "vocabulary": "
|
|
10
|
+
* `{"optionsRef": {"level": "Vendor", "vocabulary": "phone-catalog"}}`.
|
|
11
11
|
* The words live in the vocabulary the pointer names, which is a different
|
|
12
12
|
* service with a different client. So the two label sources this pair already
|
|
13
13
|
* has both come up empty: the answer's `facet_labels` because the deployed
|