Repository navigation
feat(ops): QIR scaffold + --ops flag (doc-only behavior) - #40
Conversation
…ures: QueryPlan/Relation/Projection/Expr/Predicate\n- Deterministic alias allocator for tests\n- Unit test validates basic construction and EXISTS predicate
…ops <dir> option to generate\n- Validates presence of ops directory and common filenames\n- Logs informational message; no generation yet
…der=ops, target=function, RLS reliance=prefer\n- Guardrails: nestedList.requireLimit/requireOrderBy booleans\n- Validates target and rlsReliance
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
|
Docs-only behavior: this adds QIR node scaffolding, a no-op --ops flag, and config knobs. No generation changes or workflow edits. Targeting the feature branch to keep the surface area minimal. |
🚢 SHIPME[REALM] PASS — sha e3d4027 |
This PR lands the smallest possible scaffold to de-risk the QIR feature proposed in RFC #19, without changing generation behavior:
--ops <dir>flag recognized ingenerateas a no-op validator (logs only)opssection and validation (folder/target/guardrails/RLS reliance)--opsand links the RFC draftNotes
Targets base branch:
feat/rfc-query-ops-qir.