nocobase-app-plugin-repository-example

Call api.repository(name).findMany(options) with a JSON AST to get an array response, or iterate with for await to receive framed NDJSON records as they stream. Each query supports only one consumption mode, so create separate queries for array and streamed results.

Use relation mutation operations on hasOne, hasMany, or belongsToMany relations: create, connect, disconnect, set, update, upsert, and delete, with 20 supported combinations. Set applies only to to-many relations, and many-to-many tag operations permit only the role through field.

Yes, orders use optimistic locking via a version field. Preserve version when editing and send ifVersion with updates; on a 409 conflict, refresh the record rather than overwriting it.

A Repository Policy defines allowed read, create, update, and delete operations per exposure, written directly or built with buildRepositoryPolicy, where unmentioned nodes are denied. Policies stay server-side; requests carrying policy or scope fields are rejected.

No, the plugin is a demonstration with no per-role or tenant authorization; every signed-in user can manage all records. A production adaptation must design its own authorization boundary and must not store unrelated application data in its tables.

Empty-set sums and price metrics return NULL by design, and AVG is unweighted. Separate panel queries are not a single snapshot, so results may differ if data changes between requests.