global-config

Global config reference

Kavo has one configuration mechanism, KavoSettings, merged through a single precedence chain (docs/internals/architecture/08-configuration.md):

built-in defaults → global (createKavo / KavoModule.forRoot) → entity (createCrud / @Kavo)
                  → operation (operations.<id>) → per-call (KavoCallOptions)

Global scope is the app's one place to state a default once instead of repeating it on every entity. Nearer scopes override farther ones key by key (scalars/objects replace; arrays replace wholesale; undefined is skipped; false disables an inheritable feature and a nearer object re-enables it).

Wiring it in a Nest app

KavoModule.forRootAsync({
  imports: [DatabaseModule.forRoot()],
  inject: [DATA_SOURCE],
  provideServices: true, // needed only if some class constructor-injects a CRUD service token
  useFactory: (dataSource: DataSource) => ({
    infrastructure: createInfrastructure(dataSource),
    defaults: {
      pagination: { defaultLimit: 20, maxLimit: 100 },
      errors: { exposeInternals: false },
      operations: { restoreOne: false }, // app-wide default; an entity can opt back in
    },
  }),
});

KavoModuleOptions (packages/frameworks/nest/src/kavo-options.ts):

interface KavoModuleOptions {
  infrastructure?: KavoInfrastructure; // e.g. createInfrastructure(dataSource)
  defaults?: DeepPartial<KavoSettings>; // passed through untouched to createKavo
  paginationStrategies?: readonly PaginationStrategy[];
}

forRoot(options) takes the object directly; forRootAsync(options) resolves it via useFactory/inject (needed to wait for a DataSource, etc.). Both also accept { provideServices: true }, which additionally provides getKavoServiceToken(Entity) for every @Kavo class seen so far — only needed when some class constructor-injects its own service; a @Kavo class itself should use boundKavoService(this) instead. In plain core (no Nest), the same object is createKavo(options).createCrud(Entity, config?).