Bump RQB core to v8.23.0

Author: jakeboone02

AGENTS.md

@@ -247,7 +247,10 @@ opposite render modes. This is structural, not cosmetic — one plugin instance
   run otherwise lands on the flush _after_ the first op and silently reverts it. Found the hard
   way: 4 of 19 cases failed with the ops apparently never applied.
 - `extract.ts` exposes both `extractFromContainer` and `extractFromMarkup` (upstream's
-  `schemaVersion` 2 split). The markup form builds its own `JSDOM` when there is no global
+  `schemaVersion` 2 split). Both walk a real DOM here, so `schemaVersion` 3's per-element `text`
+  channel (own direct text-node children only, verbatim) needs no entity decoding — upstream's
+  `decodeText` exists only because its markup walker is `HTMLRewriter`. The markup form builds its
+  own `JSDOM` when there is no global
   `DOMParser`, which is what lets the ssr project run in the `node` environment and thereby prove
   a server render needs no document.
 
@@ -294,8 +297,9 @@ The four conformance gates were each proved red and reverted:
 
 1. **DOM parity** — ` conformance-gate-probe` appended to `ActionElement.tsx`'s class turned
    exactly 100 cases red (50 static + 50 post-flush), which is the split the two projects promise.
-2. **`schemaVersion`** — `EXPECTED_SCHEMA_VERSION = 3` made `conformance:fetch` exit 1 with the
-   "update `test/conformance` before bumping the tag" message.
+2. **`schemaVersion`** — `EXPECTED_SCHEMA_VERSION = 4` made `conformance:fetch` exit 1 with the
+   "update `test/conformance` before bumping the tag" message. (Originally proved with `3` against
+   the schema-2 fixtures; it fired for real on the v8.23.0 bump.)
 3. **Scenario drift** — renaming the local `allControls` scenario turned the drift test (and the
    three case-alignment tests) red while all 50 rendered cases stayed green.
 4. **Value-editor reset** — an early `return` in `createValueEditorReset`'s apply phase left

CHANGELOG.md

@@ -16,6 +16,17 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### Changed
 
+- `@react-querybuilder/core` is bumped to **8.23.0**, and the conformance fixtures with it
+  (`CONFORMANCE_TAG` v8.22.4 → v8.23.0, `schemaVersion` 2 → 3). Schema 3 adds a per-element `text`
+  channel — the element's own direct text-node children, verbatim — so `extract.ts` now emits it.
+  Both walkers here go through a real DOM, so entity decoding is free. All 237 conformance
+  assertions stay green; the new channel was proved live (a leading space added to every
+  `ActionElement` label turns 100 cases red, a change the class-only schema-2 surface could not
+  see).
+- `controlKeys` is now re-exported explicitly from the barrel. Core 8.23.0 exports a `controlKeys`
+  of its own, and two star exports cannot disambiguate themselves (TS2308). This package's list is
+  the deliberate delta — it omits `dragHandle`, `ruleGroupHeaderElements`, and
+  `ruleGroupBodyElements`, matching this package's `Controls` — so it wins.
 - **Breaking:** `createQueryBuilderState` is renamed **`createQueryBuilder`** and is now documented
   as the package's headless entry point (see "Headless usage" in the README). It already was one —
   it returns query, tree, manager, schema, actions and context and renders nothing — so this is a

bun.lock

@@ -10,7 +10,7 @@
     "check": "tsc --noEmit -p tsconfig.json"
   },
   "dependencies": {
-    "@react-querybuilder/core": "^8.22.5",
+    "@react-querybuilder/core": "^8.23.0",
     "@solidjs/web": "2.0.0-rc.0",
     "solid-js": "2.0.0-rc.0"
   },

examples/demo/package.json

@@ -10,7 +10,7 @@
     "test:ssr": "bun run ./ssr-smoke-test.ts"
   },
   "dependencies": {
-    "@react-querybuilder/core": "^8.22.5",
+    "@react-querybuilder/core": "^8.23.0",
     "@solidjs/web": "2.0.0-rc.0",
     "solid-js": "2.0.0-rc.0",
     "solid-querybuilder": "workspace:*"

examples/ssr/package.json

@@ -68,7 +68,7 @@
     "@solidjs/web": "^2.0.0-rc.0"
   },
   "dependencies": {
-    "@react-querybuilder/core": "^8.22.5"
+    "@react-querybuilder/core": "^8.23.0"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.5",

packages/solid-querybuilder/package.json

@@ -19,13 +19,13 @@ import * as path from 'node:path';
  * The upstream release whose fixtures this port is verified against. Bump deliberately, and
  * expect a diff in the conformance tests when you do.
  */
-export const CONFORMANCE_TAG = 'v8.22.4';
+export const CONFORMANCE_TAG = 'v8.23.0';
 
 /**
  * The fixture *shape* version. Not the tag: upstream may cut a dozen releases without changing
  * the schema, and a schema change must fail loudly rather than be mis-read.
  */
-export const EXPECTED_SCHEMA_VERSION = 2;
+export const EXPECTED_SCHEMA_VERSION = 3;
 
 const ASSET = 'rqb-conformance-fixtures.tar.gz';
 const RELEASE_URL = `https://github.com/react-querybuilder/react-querybuilder/releases/download/${CONFORMANCE_TAG}`;

packages/solid-querybuilder/scripts/fetch-fixtures.ts

@@ -11,4 +11,9 @@ export * from './actions.js';
 export * from './components/index.js';
 export { Label } from './internal/Label.jsx';
 export * from './reactive/index.js';
+// Two stars can't disambiguate themselves: core 8.23 added its own `controlKeys`, which collides
+// with the port's (TS2308). The port's list is the deliberate delta — it omits `dragHandle`,
+// `ruleGroupHeaderElements`, and `ruleGroupBodyElements`, matching this package's `Controls` —
+// so it is re-exported explicitly to win.
+export { controlKeys } from './reactive/context.js';
 export type * from './types/index.js';

packages/solid-querybuilder/src/index.tsx

@@ -1,5 +1,5 @@
 /**
- * The class surface *after* effects have flushed, asserted against the `schemaVersion` 2
+ * The class surface *after* effects have flushed, asserted against the `schemaVersion` 3
  * `classnames-post-flush.json` layer.
  *
  * Rendered **uncontrolled** (`defaultQuery`, no `onQueryChange`), exactly as upstream generated

packages/solid-querybuilder/test/conformance/classnames-post-flush.test.ts

@@ -33,6 +33,17 @@ export interface ClassNameEntry {
   path?: string;
   /** The verbatim `class` attribute. Whitespace is preserved; this is a byte-level claim. */
   className: string;
+  /**
+   * The concatenation of this element's *own* direct text-node children, verbatim — no trimming,
+   * no collapsing, no descendant text. `''` when there are none (present, not omitted, so the
+   * key set is stable). Added by `schemaVersion` 3.
+   *
+   * Verbatim is the point: it catches a stray space in a label or a whitespace text node emitted
+   * by a template compiler, both invisible under any normalization. Both walkers here go through
+   * a real DOM, so character references are decoded for free — upstream's `decodeText` exists
+   * only because its markup walker is `HTMLRewriter`, which reports raw source text.
+   */
+  text: string;
 }
 
 /** The accessible description (`title`) of one rule group. */
@@ -75,6 +86,12 @@ export const extractFromContainer = (container: Element): ExtractResult => {
         ...(testID === undefined ? {} : { testID }),
         ...(path === undefined ? {} : { path }),
         className,
+        // Direct text-node children only, in document order. `Node.TEXT_NODE` is spelled `3` so
+        // this works against whatever DOM implementation is in play (jsdom in either project).
+        text: [...element.childNodes]
+          .filter(node => node.nodeType === 3)
+          .map(node => node.nodeValue ?? '')
+          .join(''),
       });
     }