feat(plugins): hosted Tabularium registry + connection catalogue (fully BC) by NewtTheWolf · Pull Request #299 · TabularisDB/tabularis

NewtTheWolf · 2026-06-07T12:54:38Z

What

Wires up the hosted Tabularium registry (registry.tabularis.dev) and rebuilds
the New Connection flow around a driver catalogue — without breaking the old
registry format.

45 files · +4578 / −523

Backend

Hosted registry + merge — new HTTP API catalogue merged with the legacy
registry (union, API wins on id conflict), so old plugins (duckdb, …) stay
visible. (registry.rs, commands.rs)
Deep-link install — tabularis://install handler, version-aware via
semver: Install / Update / already-installed. (deep_link.rs)
Tracked downloads — assets resolve through the registry redirect endpoint
(/latest unpinned, /releases/{version} pinned) so installs get counted.
(tabularium.rs)
Removable BC layer — all compat code in compat.rs, tagged
COMPAT(registry-ga): at every call site. Legacy registry.json install +
listing and legacy manifest.json still work; deletable once all plugins
have migrated.

Frontend

Connection catalogue as step 1 of New Connection: search, paradigm
facets, engine cards, version picker, install-gated uninstalled drivers with
inline install. (ConnectionCatalogue, EngineCard, InstallGate, …)
PluginInstallConfirmModal renders the deep-link action (install / update /
already-installed).
i18n across all 7 locales.

Compatibility

Fully backwards-compatible: the legacy registry format and manifest.json are
still consumed. The in-repo plugins/registry.json seed is replaced by
tabularium-extensions.schema.json; the legacy format is read from the hosted
source via the BC layer.

Tests

Backend 688 ✓ · Frontend 2535 ✓

tabularium-sdk 0.2 exposes verified/extensions fields used by the registry integration. semver is used for version-aware install classification (install vs update vs already-installed).

…C layer Integrate the hosted Tabularium registry (registry.tabularis.dev) alongside the legacy static registry.json, with version-aware deep-link install. - Merge new HTTP API catalogue with legacy registry.json (union, API wins on id conflict) so old plugins (duckdb, ...) stay visible. - Semver-aware install classification: install / update / already-installed. - Tracked asset downloads via the registry redirect endpoint: /api/plugins/{slug}/latest for unpinned, /releases/{version} for pinned. - Host manifest parser migrated to .tabularium (JSON), legacy manifest.json read as fallback. All backwards-compat code lives in plugins/compat.rs and is marked with `COMPAT(registry-ga):` at every call site, so it can be removed mechanically once all plugins have migrated to the hosted registry.

Redesign the New Connection flow around a searchable driver catalogue that merges built-in drivers with registry plugins. - EngineCard, ConnectionCatalogue (search + paradigm facets + grid), DriverVersionPicker, InstallBanner, InstallGate components. - useConnectionCatalogue hook + connectionCatalogue normalization model. - Catalogue is step 1 of the New Connection wizard; uninstalled drivers are install-gated with inline driver install.

PluginInstallConfirmModal now renders the install action returned by the preview command: Install, Update (when a newer version exists), or an already-installed banner for an up-to-date plugin. - useDeepLinkInstall hook drives the tabularis://install flow. - PluginsTab consumes the registry base URL per plugin for its registry link.

Add registry/catalogue and deepLink (updateConfirm, alreadyInstalled) strings across all 7 locales.

…tion # Conflicts: # tests/setup.ts

- NewConnectionModal: remove unused PluginManifest import. - PluginInstallConfirmModal: key the modal by request in App.tsx so each request remounts with fresh state, replacing the synchronous state reset inside the effect (react-hooks/set-state-in-effect). Loading state now initialises from the keyed mount; the effect only sets state in its async callbacks.

kilo-code-bot · 2026-06-07T13:10:40Z

Code Review Summary

Status: No Issues Found | Recommendation: Merge

All 4 previously identified issues have been resolved in commit 4d4368c.

Resolved Issues

File	Line	Issue	Status
`src-tauri/src/plugins/commands.rs`	45	Static registry plugins no longer receive broken detail-page links	✅ Fixed
`src-tauri/src/plugins/registry.rs`	185	Detail fetches now use `futures::future::join_all` for parallelism	✅ Fixed
`src/hooks/useConnectionCatalogue.ts`	71	Replaced `in` operator with `Object.prototype.hasOwnProperty.call`	✅ Fixed
`src/components/modals/PluginInstallConfirmModal.tsx`	70	Empty `version` string now treated as nullish via `

Files Reviewed (4 files)

src-tauri/src/plugins/commands.rs
src-tauri/src/plugins/registry.rs
src/hooks/useConnectionCatalogue.ts
src/components/modals/PluginInstallConfirmModal.tsx

Previous Review Summary (commit 2cbb015)

Current summary above is authoritative. Previous snapshots are kept for context only.

Previous review (commit `2cbb015`)

Status: No Issues Found | Recommendation: Merge

All 4 previously identified issues have been resolved in commit 4d4368c.

Resolved Issues

File	Line	Issue	Status
`src-tauri/src/plugins/commands.rs`	45	Static registry plugins no longer receive broken detail-page links	✅ Fixed
`src-tauri/src/plugins/registry.rs`	185	Detail fetches now use `futures::future::join_all` for parallelism	✅ Fixed
`src/hooks/useConnectionCatalogue.ts`	71	Replaced `in` operator with `Object.prototype.hasOwnProperty.call`	✅ Fixed
`src/components/modals/PluginInstallConfirmModal.tsx`	70	Empty `version` string now treated as nullish via `

Files Reviewed (4 files)

src-tauri/src/plugins/commands.rs
src-tauri/src/plugins/registry.rs
src/hooks/useConnectionCatalogue.ts
src/components/modals/PluginInstallConfirmModal.tsx

_{Reviewed by nemotron-3-ultra-550b-a55b-20260604:free · Input: 168.2K · Output: 2.5K · Cached: 2.2K}

…y version) - commands.rs: only set registry_base_url for a real Tabularium API, not a legacy `.json` base (avoids broken `…/registry.json/plugins/<id>` links). - registry.rs: fetch plugin details concurrently via join_all instead of N sequential round-trips. - useConnectionCatalogue: use hasOwnProperty instead of `in` so plugin ids like "constructor"/"toString" aren't matched against Object.prototype. - PluginInstallConfirmModal: treat empty `?version=` as no pin (|| null) for both the preview fetch and the displayed target version.

…catalogue sort Addresses PR review (debba): - Restore plugins/registry.json instead of deleting it. LEGACY_REGISTRY_URL points at this file on main; deleting it would 404 after merge, silently dropping un-migrated plugins from resolve_registry's merge and breaking already-shipped app versions that use it as their only registry source. Prune only when the whole COMPAT(registry-ga) layer is removed. - Sort engine groups builtins-first then other-last (then alphabetical), so the catalogue leads with the SQL section and pushes the metadata-less 'Other' section to the end instead of opening on a wall of legacy plugins.

…ration

…-ready CI - scaffold emits .tabularium (was manifest.json); keep id=slug/name=display so the host identity/display split is preserved - add `migrate [path]` to convert legacy manifest.json plugins to .tabularium; drops a redundant id (id===name), refuses without a semver version - `migrate --ci` regenerates release.yml from the registry-ready template (BIN_NAME from manifest.executable); without --ci the workflow is left as-is, only its manifest.json reference is renamed - release.yml template: stash artifacts + single release job publishing .tabularium as a standalone asset (Tabularium registry resolves the manifest from release assets); assets/ dir support; action version bumps - plugin-api: doc comments reference .tabularium - bump @tabularis/create-plugin 0.1.1 -> 0.2.0

NewtTheWolf · 2026-06-12T07:59:54Z

@debba small follow-up on this branch (2cbb015) — I aligned packages/ with the new .tabularium host contract and added tooling so plugin authors can keep up:

@tabularis/create-plugin (0.1.1 → 0.2.0)

Scaffold now emits .tabularium instead of manifest.json. id=slug / name=display are deliberately kept, because the host falls back to name as the identity when id is absent (otherwise the display name would become the slug).
New command migrate [path]: converts existing manifest.json plugins → .tabularium, drops a redundant id (only when id===name), and refuses without a semver version (registry requirement). justfile/README/release.yml references are carried along.
migrate --ci: additionally regenerates release.yml from the registry-ready template (BIN_NAME derived from manifest.executable). Without --ci the CI structure is left untouched — only its manifest.json reference is renamed so the build keeps working.

Registry-ready release workflow (template)
The previous template workflow only bundled .tabularium inside the platform zips. But the hosted Tabularium registry resolves the manifest from the release assets (since 0.8.0), not from the git ref. The workflow now stashes the artifacts and, in a separate release job, uploads the zips plus .tabularium as a standalone asset (modeled on my firestore plugin CI). I deliberately left out the Codeberg publish — that's a hosting choice, not generic.

@tabularis/plugin-api: doc comments updated to reference .tabularium only.

Tests: 32 green (8 new for migrate, incl. --ci regeneration + edge cases), tsc/build clean, generated YAML validated. Happy to hear if the migrate defaults (id handling, CI only with --ci) look right to you.

debba · 2026-06-12T13:01:53Z

That's awesome! Thanks @NewtTheWolf !

The published dist called copyTemplate('ui-extension-locales', ...) but that template dir never existed, so --with-ui crashed; source had dropped the call, so no locales were emitted at all. Restore the feature properly: - add templates/ui-extension-locales/locales/en.json.tmpl (plugin-root locales) - scaffold copies it under --with-ui - ui template uses usePluginTranslation instead of a hardcoded string - smoke asserts locales/en.json exists for --with-ui

…tion # Conflicts: # src/components/modals/NewConnectionModal.tsx

…iver support Surface registry engine/paradigms on manifests so locally-installed (not yet published) plugin drivers appear in the connection picker instead of loading invisibly. Add single_database capability to skip the database tab/field for flat stores (e.g. Meilisearch).

NewtTheWolf added 7 commits June 7, 2026 08:25

chore(deps): bump tabularium-sdk to 0.2, add semver

85bf2d8

tabularium-sdk 0.2 exposes verified/extensions fields used by the registry integration. semver is used for version-aware install classification (install vs update vs already-installed).

feat(i18n): translations for catalogue + deep-link install

0bc176e

Add registry/catalogue and deepLink (updateConfirm, alreadyInstalled) strings across all 7 locales.

Merge remote-tracking branch 'origin/main' into feat/registry-integra…

f02f6ea

…tion # Conflicts: # tests/setup.ts

kilo-code-bot Bot reviewed Jun 7, 2026

View reviewed changes

Comment thread src-tauri/src/plugins/commands.rs Outdated

Comment thread src-tauri/src/plugins/registry.rs Outdated

Comment thread src/hooks/useConnectionCatalogue.ts Outdated

Comment thread src/components/modals/PluginInstallConfirmModal.tsx Outdated

debba mentioned this pull request Jun 10, 2026

External plugin host support gaps found while building a DM / Dameng driver #316

Open

debba reviewed Jun 11, 2026

View reviewed changes

Comment thread src-tauri/src/plugins/compat.rs

debba reviewed Jun 11, 2026

View reviewed changes

Comment thread src/utils/connectionCatalogue.ts Outdated

NewtTheWolf added 3 commits June 11, 2026 19:59

Merge remote-tracking branch 'upstream/main' into feat/registry-integ…

4c658f3

…ration

debba force-pushed the main branch from f48e73e to dedbca3 Compare June 16, 2026 11:07

NewtTheWolf mentioned this pull request Jun 16, 2026

Forward external plugin trigger RPCs #321

Merged

NewtTheWolf added 3 commits June 25, 2026 15:38

Merge remote-tracking branch 'origin/main' into feat/registry-integra…

78f8bc3

…tion # Conflicts: # src/components/modals/NewConnectionModal.tsx

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

feat(plugins): hosted Tabularium registry + connection catalogue (fully BC)#299

feat(plugins): hosted Tabularium registry + connection catalogue (fully BC)#299
NewtTheWolf wants to merge 14 commits into
TabularisDB:mainfrom
NewtTheWolf:feat/registry-integration

NewtTheWolf commented Jun 7, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kilo-code-bot Bot commented Jun 7, 2026 •

edited

Loading

Previous review (commit `2cbb015`)

Uh oh!

Uh oh!

Uh oh!

NewtTheWolf commented Jun 12, 2026 •

edited

Loading

Uh oh!

debba commented Jun 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

NewtTheWolf commented Jun 7, 2026

What

Backend

Frontend

Compatibility

Tests

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kilo-code-bot Bot commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Summary

Previous review (commit 2cbb015)

Uh oh!

Uh oh!

Uh oh!

NewtTheWolf commented Jun 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

debba commented Jun 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

kilo-code-bot Bot commented Jun 7, 2026 •

edited

Loading

Previous review (commit `2cbb015`)

NewtTheWolf commented Jun 12, 2026 •

edited

Loading