flo-bit.dev / contrail

0

[READ-ONLY] Mirror of https://github.com/flo-bit/contrail. atproto backend in a bottle flo-bit.dev/contrail/

0

contrail / packages / lexicons /

at changeset-release/main 3 folders 7 files

github-actions[bot] Version Packages 5w ago

lexicon-templates

phase 7c

2 months ago

fix(contrail): ingest and index NSID-keyed collections A collection can be keyed directly by its NSID, with the `collection` field omitted (the map key is itself the NSID). That shape was only half-supported: records landed in the records table, but the rest of the pipeline silently skipped these collections. - Config: make CollectionConfig.collection optional. resolveConfig normalizes an omitted value to the map key once; validateConfig accepts NSID-keyed entries (dotted keys with no collection field). Every collection-list and lookup helper resolves `collection ?? key`, so behavior is correct on both raw and resolved configs. - Ingest: getCollectionNsids / getDiscoverableNsids / getDependentNsids no longer return undefined, so Jetstream subscription and backfill now include NSID-keyed collections, and notify resolves shortNameForNsid instead of rejecting "collection not tracked". - Search: buildFtsStatements and lookupExistingRecords resolve the storage key the same way, so FTS is populated and replay/update detection works for NSID-keyed collections (previously full-text search stayed empty for them). - A resolveCollectionKey(config, nsid) helper in contrail-base returns the storage key (short alias, or the NSID itself when keyed directly), or null when unknown, de-duplicating the fallback the insert path inlined. Every change is a type-widening or a fallback that only fires when `collection` is absent, so existing alias-keyed configs are unchanged. Tests: config-layer unit tests (resolveConfig / validateConfig for NSID-keyed entries), the resolve-collection-key helper, an end-to-end notify-to-ingest test, and the existing search.test.ts (which uses an NSID-keyed config and was the failing regression). Full suite green. Changeset included.

1 month ago

merge: resolve conflicts with main into feat/another-big-refactor Main added record-filter, identity-events, follow-feed, and lex-gen-fix features in `packages/contrail/src/core/*` that PR #30 had reorganized into the new package split. Each conflict resolved by: 1. Keeping PR #30's re-export shims in `packages/contrail/src/core/*` (these files now `export * from "@atmo-dev/contrail-appview"`) 2. Porting main's additions to the corresponding files in `packages/contrail-appview/src/core/*`, which is the new home of the actual implementation. Files re-shimmed: - backfill.ts, db/records.ts, db/schema.ts, identity.ts, jetstream.ts, persistent.ts, router/feed.ts, types.ts Ports landed in contrail-appview/src/core (or contrail-base where types and identity helpers actually live): - backfill.ts, db/records.ts, db/schema.ts, jetstream.ts, persistent.ts, router/feed.ts (+1.0K lines from main) - constellation.ts (new 181-line module) - contrail-base/src/types.ts: FeedTargetConfig, ConstellationConfig, buildFeedTargetCaps, normalizeFeedTarget, feedTargetMaxItems, CollectionConfig.{timeField, subjectField, recordFilter}, and resolveConfig defaulting `discover: false` for `app.bsky.*` - contrail-base/src/identity.ts: applyIdentityEvent (handle change handler) Test mock for `persistent.test.ts` updated to mock `@atmo-dev/contrail-base` (post-split home of identity helpers) and include both `refreshStaleIdentities` and `applyIdentityEvent`. Test status post-merge: 314 passed, 7 failed in `packages/contrail/tests/search.test.ts` — these 7 failures pre-exist on plain `origin/main` and are unrelated to the merge. No behavior changes intended beyond what main and PR #30 already deliver.

2 months ago

Version Packages

1 month ago

monorepo

3 months ago

Version Packages

1 month ago

tsconfig.build.json

monorepo

3 months ago

monorepo

3 months ago

monorepo

3 months ago

vitest.config.ts

monorepo

3 months ago

README.md

@atmo-dev/contrail-lexicons#

Generate atproto lexicon JSON from a contrail config, and (optionally) drive the full @atcute/lex-cli pull + type-generation pipeline from a single command.

Install#

pnpm add -D @atmo-dev/contrail-lexicons @atcute/lex-cli

@atcute/lex-cli is a peer dep — you pin the version.

CLI#

contrail-lex generate   # emit lexicon JSON from your Contrail config
contrail-lex pull       # wraps `lex-cli pull`
contrail-lex types      # wraps `lex-cli generate`
contrail-lex all        # generate → pull → generate → pull → types
contrail-lex all --no-types   # skip the final type-generation step

The CLI auto-detects your Contrail config at contrail.config.ts, app/config.ts, or src/lib/contrail/config.ts (first match wins). Override with --config <path>.

For anything the all subcommand doesn't cover — custom output dirs, extra pull sources, multiple lex.config.js files — call lex-cli directly. This package doesn't hide or replace it.

Programmatic API#

import { generateLexicons } from "@atmo-dev/contrail-lexicons";

const generated = generateLexicons({
  config,
  rootDir: process.cwd(),
  outputDir: "lexicons-generated",
});

See also: extractXrpcMethods, listXrpcMethods, publishLexicons.