@uniweb/core 0.37.1 → 0.37.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.
Files changed (2) hide show
  1. package/package.json +3 -3
  2. package/src/records-service.js +10 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uniweb/core",
3
- "version": "0.37.1",
3
+ "version": "0.37.2",
4
4
  "description": "Core classes for the Uniweb platform - Uniweb, Website, Page, Block",
5
5
  "type": "module",
6
6
  "exports": {
@@ -49,8 +49,8 @@
49
49
  "vitest": "^4.1.7"
50
50
  },
51
51
  "dependencies": {
52
- "@uniweb/theming": "^0.2.0",
53
- "@uniweb/semantic-parser": "^1.5.1"
52
+ "@uniweb/semantic-parser": "^1.5.1",
53
+ "@uniweb/theming": "^0.2.0"
54
54
  },
55
55
  "scripts": {
56
56
  "test": "vitest run"
package/src/records-service.js CHANGED
@@ -36,13 +36,16 @@
36
36
  *
37
37
  * ## ⛔ The HOST tier only — and the reason is mechanical, not a policy
38
38
  *
39
- * `resolveService` reads the site's authored tier first and the host's second.
40
- * This does not, because it cannot: its caller `resolveFetchConfigs` is a leaf
41
- * that runs in an SSR isolate over a plain content object with no `Website` to
42
- * hand. It reads `config.services` directly, so the authored tier is not
43
- * available here. ⇒ **A site does not declare its own record provider**, which
44
- * is also the standing ruling — a third-party source is a foundation transport,
45
- * not site-level config *(2026-09-04, the retired `fetcher:` vocabulary)*.
39
+ * `resolveService` reads two tiers: the host's offer, then the site's authored
40
+ * declaration for what the host does not offer. *(This said "the site's authored
41
+ * tier first" until 2026-10-06; the host's offer has come first since 2026-09-10.)*
42
+ * This reads the host's alone, because it cannot read the other: its caller
43
+ * `resolveFetchConfigs` is a leaf that runs in an SSR isolate over a plain
44
+ * content object with no `Website` to hand. It reads `config.services` directly,
45
+ * so the authored tier is not available here. ⇒ **A site does not declare its
46
+ * own record provider**, which is also the standing ruling — a third-party
47
+ * source is a foundation transport, not site-level config *(2026-09-04, the
48
+ * retired `fetcher:` vocabulary)*.
46
49
  *
47
50
  * ## ⛔ A pattern, not a base — and the reason is a deleted function
48
51
  *