WIP: feat: expose tag and custom-field values through core reads #48

2026-10-26T13:21:55Z

KofTwentyTwo commented

2026-10-26 13:21:55 +00:00

(Migrated from github.com)

Selecting collaboration tag or EAV virtual fields previously did not populate their values through ordinary core reads. This adds batched value providers so Query/Get, HTTP responses and exports include approved tag labels and typed custom-field values while preserving host post-query customizers, parent/field authorization and the originating transaction.

The default core BOM is the published 4.1.0-virtual-field-values-1196-cc3981bb3-SNAPSHOT. Its publisher passed, and an independent initially empty-cache consumer downloaded the timestamped BOM/core and compiled the new API. Artifact hashes and upgrade sequencing are recorded in docs/VIRTUAL-FIELD-UPGRADE.md.

Validation: full wrapper verify with the default published pin passed 198 tests, zero failures/errors/skips, packaging and coverage. Coverage includes HTTP/export selection, 11 EAV value types, real PostgreSQL commit/rollback and definition transaction cases, tenant/field restrictions, tag label changes and Redis presence.

This does not enable EAV writes or SQL DISTINCT/sorting/aggregation over provider-generated values. Backend identity is required, including explicit fetching for joined heavy primary keys. The consumer snapshot is published as 0.1.0-field-values-1196-ecff347-SNAPSHOT (publisher 168 succeeded; timestamp 20261026.133203-1). A second independent empty-cache Java 21 consumer compiled both published collaboration providers against the published core API; exact POM/JAR checksums are recorded in the upgrade guide. Integrated Kof22 adoption remains unqualified. This branch targets feature/collab and does not yet combine the independent attachment, My Work and recovery follow-ups.

Tracks QRun-IO/qqq#1196 and consumes core PR1322's published feature snapshot. No merge or deployment; the issue remains open pending integration and host adoption.

Selecting collaboration tag or EAV virtual fields previously did not populate their values through ordinary core reads. This adds batched value providers so Query/Get, HTTP responses and exports include approved tag labels and typed custom-field values while preserving host post-query customizers, parent/field authorization and the originating transaction. The default core BOM is the published `4.1.0-virtual-field-values-1196-cc3981bb3-SNAPSHOT`. Its publisher passed, and an independent initially empty-cache consumer downloaded the timestamped BOM/core and compiled the new API. Artifact hashes and upgrade sequencing are recorded in docs/VIRTUAL-FIELD-UPGRADE.md. Validation: full wrapper verify with the default published pin passed 198 tests, zero failures/errors/skips, packaging and coverage. Coverage includes HTTP/export selection, 11 EAV value types, real PostgreSQL commit/rollback and definition transaction cases, tenant/field restrictions, tag label changes and Redis presence. This does not enable EAV writes or SQL DISTINCT/sorting/aggregation over provider-generated values. Backend identity is required, including explicit fetching for joined heavy primary keys. The consumer snapshot is published as `0.1.0-field-values-1196-ecff347-SNAPSHOT` (publisher 168 succeeded; timestamp `20261026.133203-1`). A second independent empty-cache Java 21 consumer compiled both published collaboration providers against the published core API; exact POM/JAR checksums are recorded in the upgrade guide. Integrated Kof22 adoption remains unqualified. This branch targets feature/collab and does not yet combine the independent attachment, My Work and recovery follow-ups. Tracks QRun-IO/qqq#1196 and consumes core PR1322's published feature snapshot. No merge or deployment; the issue remains open pending integration and host adoption.

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This pull request is marked as a work in progress.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feature/field-values-1196:feature/field-values-1196

git checkout feature/field-values-1196

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-collaboration#48