AccessConditionResult
Defined in: packages/core/src/access/constraintTypes.ts:274
Terminal marker for a completed access CONDITION — the value a rule’s
constraints callback returns.
Deliberately NOT ConstraintResult. That one marks a completed
expression inside one algebra’s callback; this marks a completed condition on
the query as a whole. Keeping them separate is what makes the mistake
unrepresentable: FilterConstraintBuilder.and takes ConstraintResult, so an
index condition can never be passed into a boolean combinator. Under a single
shared terminal it type-checked and produced a filter node with no kind, which
the compilers silently turned into undefined — a rule that appeared to
constrain and did not.
Nominal for the same reason as ConstraintResult: a plain object literal must
not satisfy it, so only a real q.withIndex(…) / q.filter(…) call can produce
one.
Extended by
Section titled “Extended by”Constructors
Section titled “Constructors”Constructor
Section titled “Constructor”new AccessConditionResult():
AccessConditionResult
Returns
Section titled “Returns”AccessConditionResult