Changelog - 2026-09-17

@venizia/ignis-kernel/repository

Feature

import { AbstractDataSource, AbstractRepository } from '@venizia/ignis-kernel/repository';
import type { TFilter, TWhere } from '@venizia/ignis-kernel/repository';

Entry	Browser bundle
base/repositories through the root barrel	105.3 KB gzipped
@venizia/ignis-kernel/repository	14.7 KB gzipped

Why it exists

A repository talks to a datasource. AbstractDataSource is engine-neutral - its only required member is configure() - so an HTTP request to another server is a datasource in the same sense Drizzle-over-Postgres is one: same role, different transport. Nothing in AbstractRepository binds it to SQL; it is generic over plain objects and holds an AbstractDataSource.

Both halves already speak @venizia/ignis-filter, so a consumer on another transport shares where/order/limit/skip rather than translating into its own vocabulary.

What stopped that was packaging, not design: base/repositories reaches query-schemas and a CountSchema, so the OpenAPI layer came with the contract.

What moved

CountSchema left common/types/results.ts for common/types/result-schemas.ts, and TCount is now written out as { count: number } rather than inferred from it. z.object() runs at module load, so inferring the type from the schema put zod on every path that needed the type.

Both files are re-exported from the same barrel. No import path changes.

What it carries

AbstractRepository, AbstractDataSource, IDataSource, the CRUD contract interfaces (IRepository, IReadableRepository, ICreatableRepository, IUpdatableRepository, IDeletableRepository, IPersistableRepository, ICrudRepository), buildDataRange, TCount, TDataRange, TDataWithRange, and the filter vocabulary.

Listed export by export, like ./metadata: a sub-path is a surface someone decided on, not whatever a directory grows into. A guard test fails over 120 KB or on zod reaching it.

What a consumer has to write

Four things are easy to guess wrong, so the shape is kept as a compile-checked fixture (src/__tests__/repository-contract-shape.ts) rather than described in prose:

• AbstractRepository demands twelve abstract members. A read-only resource would have to stub create, updateById and deleteById. Implement IReadableRepository instead - five members, and it is what a read-only transport actually is.
• find is an overload with a range variant. One signature does not satisfy it; both have to be declared.
• IRepository names dataSource, entity and getEntity. AbstractEntity is exported from this entry for that reason - it is engine-neutral too: a name, getSchema({ type }), an id type.
• AbstractDataSource declares name/settings/schema as fields with no constructor that sets them. A subclass assigns them itself.

class HttpDataSource extends AbstractDataSource<{ baseUrl: string }> {
  override name = 'http';
  override settings: { baseUrl: string };
  override schema = {} as never;

  constructor(opts: { baseUrl: string }) {
    super({ scope: HttpDataSource.name });
    this.settings = { baseUrl: opts.baseUrl };
  }

  async configure(): Promise<void> {}
}

Who is affected

Nobody, at the API. A new entry point; the root barrel is unchanged.

Files:

• packages/kernel/src/repository.ts
• packages/kernel/src/base/repositories/common/types/result-schemas.ts