Skip to content

docs: fix stale manual-install plugin paths and README gaps - #49

Open
aesslinger wants to merge 2 commits into
mainfrom
docs/fix-manual-install-plugin-paths
Open

docs: fix stale manual-install plugin paths and README gaps#49
aesslinger wants to merge 2 commits into
mainfrom
docs/fix-manual-install-plugin-paths

Conversation

@aesslinger

Copy link
Copy Markdown
Collaborator

Summary

  • Fixes stale macOS/Windows manual-install plugin paths in README and justfile — Tabularis unified its plugin data directory under tabularis (dropping the legacy com.debba.tabularis / %APPDATA%\debba\tabularis\data layout) before the v0.20.0 minimum this plugin requires, but the docs still referenced the old path.
  • Adds initialize/shutdown to the Supported Operations table (real dispatched RPC methods missing from the docs).
  • Adds Ranges and Arrays rows to the Supported Data Types table — the plugin already decodes these (extract.rs), but they weren't documented.
  • Fixes the Table of Contents: adds the missing Maintainers entry, removes an inconsistent lone H3 sub-bullet.

Test plan

  • npx markdownlint README.md clean
  • Verified new plugin path against Tabularis's paths.rs/installer.rs (ProjectDirs::from("", "", "tabularis")) and the ef9716ed fix commit that migrated off com.debba.tabularis
  • Verified RPC method list against src/rpc.rs's dispatch table
  • Verified range/array type support against src/extract.rs

Tabularis unified its plugin data directory under `tabularis` (dropping the
legacy `com.debba.tabularis`/`%APPDATA%\debba\tabularis\data` layout) before
the v0.20.0 minimum this plugin requires, but the README and justfile's
dev-install/uninstall recipes still pointed at the old path. Also fills gaps
found during a full accuracy audit: the Supported Operations table was
missing the `initialize`/`shutdown` RPC methods, the data types table
omitted range and array types the plugin already decodes, and the TOC was
missing a Maintainers entry.
@aesslinger aesslinger added the prerelease:alpha Version suggestion targets an alpha prerelease label Aug 19, 2026
CP-5 previously tied the stable release to Phase 2 completion (sequences +
JSONB + extension types). Decided instead: 1.0.0 ships once the post-CP-4
beta bake-in against Tabularis 0.20.0+ shows no new correctness bugs,
independent of Phase 2 scope. Phase 2 features then version as ordinary
feat: minor bumps from 1.0.0, and CP-5 becomes a feature-completeness
milestone on an already-stable release rather than a second promotion
event.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prerelease:alpha Version suggestion targets an alpha prerelease

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant