Spaces:
Running
Running
File size: 3,906 Bytes
aa89cb5 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 | <!-- ephemeral -->
# TypeScript Assist — Create `Order Item`
Use the exact generated `Q.orderItems()` entry point. The
trusted `UserContext` supplies actor, tenant, policy, provider, and audit sink;
none of those values may be accepted from the writable input.
```typescript
import { UserContext } from '../teaql-ts';
import { Q } from './Q';
import { OrderItem } from './models/OrderItem';
export interface CreateOrderItemInput {
customerOrder: string | number;
productName: string;
quantity: number;
unitPrice: number;
}
export async function createOrderItem(
input: CreateOrderItemInput,
context: UserContext,
): Promise<OrderItem> {
const entity = Q.orderItems()
.comment('what: initialize Order Item')
.purpose('why: create Order Item')
.newEntity(context);
entity.updateCustomerOrder(input.customerOrder);
entity.updateProductName(input.productName);
entity.updateQuantity(input.quantity);
entity.updateUnitPrice(input.unitPrice);
await entity
.auditAs('Create Order Item for the requested business operation')
.save(context);
return entity;
}
```
Only the generated updater methods above are writable. Constant relation
candidates, when present, are also generated and must be copied exactly:
Compile the result unchanged. Test persistence and query-back, and prove that
blank/missing intent, blank/missing audit reason, unknown fields, and attempted
trusted-context overrides fail. Do not edit generated sources.
---
## TeaQL seven-language assist contract
Apply the verified Rust semantic ceiling while using only the exact TYPESCRIPT generated and
runtime APIs. Discover APIs through the generated application AGENTS.md and progressive
model-aware Assist. Do not inspect generated domain-library source.
- Do not create plurals by appending `s` or `es`; use the centralized generated plural.
- Human and non-human entities use different generated predicate vocabularies. Preserve
forms such as “who are active” and “whose email is”; never infer them from English.
- Configure filters, projection, paging, and other query options before `purpose(...)`.
Comment may appear anywhere in the chain. Purpose enters the executable stage; execution
requires both values, but comment does not have to immediately precede purpose.
- Every execute/list/stream and every save accepts exactly one context argument:
`UserContext`. Name that argument `context`, never `runtime`; data services and global
policy are injected when the context is built. Reserve `runtime` for process-level
runtime ownership, provider/pool setup, and module assembly.
- Tenant, merchant, identity, permissions, request policy, purpose policy, hard limit,
and continuous-page cursor policy come only from trusted context, never dynamic JSON or TFP.
- If the required operation is absent after current entity/action and required field
Assist, stop that path and report MISSING_ASSIST. Do not guess an API or search the
generated library as a fallback.
- Create each application-owned source file once. After its first compile attempt,
repair only the smallest block identified by the exact compiler or test diagnostic.
Preserve unrelated code; do not rewrite the complete file as an error-recovery loop.
- Before a repair that would replace more than 25% of an existing application file,
stop and report LARGE_REWRITE_REQUEST with the file, exact diagnostic, reason, and
estimated scope. Initial creation and model-driven regeneration are not repairs.
Capability: `create`.
- Validate and allow-list writable business fields; never mass-assign dynamic JSON.
- Create through the generated request/entity API, attach a non-empty audit reason,
save with the same UserContext, and return the runtime's native save result.
- Add a negative test proving a missing audit reason cannot write.
|