mirror of
https://github.com/Kaelio/ktx.git
synced 2026-06-07 07:55:13 +02:00
* feat(cli): define full warehouse dialect contract
* test(cli): keep dialect edge tests focused
* fix(cli): stabilize dialect contract foundation
* refactor(connectors): own read-only query preparation
* refactor(connectors): resolve dialects through registry
* refactor(connectors): keep concrete dialect classes internal
* chore(workspace): enforce dialect import boundary
* refactor(cli): resolve relationship dialect at scan boundary
* refactor(cli): use dialect display parsing for entity details
* refactor(cli): use dialect display parsing for warehouse catalog
* refactor(cli): use dialect SQL in relationship workflows
* test(cli): verify solid dialect scan workflow closure
* test: split cli tests from source tree
* refactor(cli): standardize BigQuery scope listing
* feat(sqlite): implement connector scope listing
* test(connectors): cover required table listing
* feat(cli): add warehouse driver registry
* refactor(setup): route scope discovery through driver registry
* refactor(cli): route local query execution through driver registry
* refactor(historic-sql): route dialect support through driver registry
* refactor(cli): test warehouse connections through driver registry
* fix(cli): close driver registry type export gaps
* Improve setup daemon diagnostics
* refactor(setup): centralize rail-prefixed diagnostics + query-history fallback
Extract errorMessage, writePrefixedLines, and flushPrefixedBufferedCommandOutput
into clack.ts so the setup wizard, managed daemons, and embedding/agent steps
share one rail-formatted writer. setup-databases.ts also adds a
"disable query history and retry" option when the schema-context build fails
and query history is the likely culprit, surfaced via a new
failed-query-history-unavailable status.
* fix(cli): carry catalog through the picker so BigQuery/Snowflake/SQL Server scope filters match
The setup picker's KtxTableListEntry was a 2-level { schema, name }, so
qualifiedTableId always wrote db.name into enabled_tables. When BigQuery,
Snowflake, or SQL Server later ran fast ingest, their introspect step filtered
the scope set with scopedTableNames(scope, { catalog: projectId|database, db })
— catalog was non-null on the introspect side but null in the scope refs, so
every entry was rejected, the live-database adapter staged zero table files,
and detect() failed with 'Adapter "live-database" did not recognize fetched
source output'.
Align the picker boundary with the canonical 3-level KtxTableRef:
- Add catalog: string | null to KtxTableListEntry.
- BigQuery/Snowflake/SQL Server listTables populate catalog from the
resolved projectId / database; Postgres/MySQL/ClickHouse/SQLite set null.
- qualifiedTableId emits catalog.schema.name when catalog is non-null
(resolveEnabledTables already accepts the 3-part shape) and
schemasFromEnabledTables now goes through parseDottedTableEntry so it
recovers the schema correctly from both 2-part and 3-part entries.
- Export parseDottedTableEntry from enabled-tables.ts (@internal) for picker
reuse.
Update listTables expectations in all seven connector tests and the setup /
picker test fixtures. Add a picker regression test that covers the
catalog-bearing round-trip (save + refine).
* fix(cli): allow debug telemetry under opt-out env
92 lines
3.2 KiB
TypeScript
92 lines
3.2 KiB
TypeScript
import { describe, expect, it } from 'vitest';
|
|
import {
|
|
KTX_CONTEXT_BUILD_COMMANDS,
|
|
KTX_NEXT_STEP_COMMANDS,
|
|
formatNextStepLines,
|
|
formatSetupNextStepLines,
|
|
} from '../src/next-steps.js';
|
|
|
|
describe('KTX demo next steps', () => {
|
|
it('uses supported context-build commands before agent usage', () => {
|
|
expect(KTX_CONTEXT_BUILD_COMMANDS).toEqual([
|
|
{
|
|
command: 'ktx ingest',
|
|
description: 'Build or refresh agent-ready context from all configured connections',
|
|
},
|
|
{
|
|
command: 'ktx status',
|
|
description: 'Check setup and context readiness',
|
|
},
|
|
]);
|
|
});
|
|
|
|
it('uses supported final public commands', () => {
|
|
expect(KTX_NEXT_STEP_COMMANDS).toEqual([
|
|
{
|
|
command: 'ktx status --json',
|
|
description: 'Verify project setup and context readiness',
|
|
},
|
|
{
|
|
command: 'ktx sl',
|
|
description: 'Inspect generated semantic-layer sources',
|
|
},
|
|
{
|
|
command: 'ktx wiki',
|
|
description: 'Inspect generated wiki pages',
|
|
},
|
|
]);
|
|
});
|
|
|
|
it('uses only the direct CLI route for agent verification', () => {
|
|
const commands = KTX_NEXT_STEP_COMMANDS.map((step) => step.command);
|
|
|
|
expect(commands).not.toContain('ktx agent context --json');
|
|
expect(commands).toContain('ktx status --json');
|
|
expect(commands).not.toContain('ktx serve --mcp stdio --user-id local');
|
|
});
|
|
|
|
it('explains what the next-step commands are for', () => {
|
|
const rendered = formatNextStepLines().join('\n');
|
|
|
|
expect(rendered).toContain('KTX context is ready for agents.');
|
|
expect(rendered).toContain('KTX project directory');
|
|
expect(rendered).toContain('ask a data question');
|
|
expect(rendered).toContain('Verify with:');
|
|
expect(rendered).not.toContain('this directory');
|
|
expect(rendered).not.toContain('Preferred route');
|
|
expect(rendered).not.toContain('Optional MCP:');
|
|
});
|
|
|
|
it('keeps setup next steps focused on building context when the build is not ready', () => {
|
|
const rendered = formatSetupNextStepLines({
|
|
setupReady: true,
|
|
hasContextTargets: true,
|
|
contextReady: false,
|
|
agentIntegrationReady: true,
|
|
}).join('\n');
|
|
|
|
expect(rendered).toContain('Build KTX context next.');
|
|
expect(rendered).toContain('Run ingest to build database schema context before context-source ingest.');
|
|
expect(rendered).toContain('ktx ingest');
|
|
expect(rendered).not.toContain('resume');
|
|
expect(rendered).not.toContain('scan');
|
|
expect(rendered).toContain('ktx status');
|
|
expect(rendered).not.toContain('ktx agent context --json');
|
|
expect(rendered).not.toContain('ktx serve --mcp');
|
|
});
|
|
|
|
it('shows agent commands only after setup and context build are ready', () => {
|
|
const rendered = formatSetupNextStepLines({
|
|
setupReady: true,
|
|
hasContextTargets: true,
|
|
contextReady: true,
|
|
agentIntegrationReady: true,
|
|
}).join('\n');
|
|
|
|
expect(rendered).toContain('KTX context is ready for agents.');
|
|
expect(rendered).toContain('ktx status --json');
|
|
expect(rendered).not.toContain('ktx agent');
|
|
expect(rendered).not.toContain('ktx serve --mcp stdio --user-id local');
|
|
expect(rendered).not.toContain('Build KTX context next.');
|
|
});
|
|
});
|