Skip to content

0.8.0 — SQL Server to C# navigation, first-run demo, and MIT license

Choose a tag to compare

@sfy257000 sfy257000 released this 09 Nov 10:14
· 11 commits to main since this release
59bd057

Trace a SQL Server table to the C# code and pages that reach it, starting with a database-free example.

Try the new first-run demo

python -m pip install --upgrade local-codebase-indexer
local-codebase-indexer demo

The bundled synthetic source tree connects a table, stored procedure, repository, service interface, controller actions, and a Razor page. The demo checks four expected relationships and reports source locations, confidence labels, exact-reference counts, and local timings. Use demo --json for the complete report or demo --output demo-orders to keep a copy in a new or empty directory. Existing files are never overwritten.

What's included

  • MIT license with SPDX package metadata and the license file in distribution artifacts.
  • English, Traditional Chinese, and Simplified Chinese READMEs focused on the SQL Server / C# maintenance workflow, with a three-step first run and a 32-second actual-output walkthrough.
  • A reproducible, source-backed case study and raw JSON/text evidence. Detailed configuration and limitations remain in docs/reference*.md.
  • Contribution guidance and issue forms for missing or incorrect navigation results.
  • Automatic official MCP Registry publication after PyPI succeeds, using GitHub OIDC and a pinned, signature-verified official publisher.

The example is synthetic. Its four checks do not establish production accuracy, runtime behavior, or measured developer time savings. Interface-based controller reachability is labeled probable. Dynamic SQL and some C# dispatch patterns still require source verification.

Validation

109 tests passed locally and against extracted source-distribution tests using the installed wheel. The isolated installed-wheel demo passes all four checks and includes all sample files and MIT metadata. Build, twine, release-version/checksum validation, official MCP manifest validation, and workflow lint pass. The 15-question project search evaluation remains Recall@5 0.533 and MRR 0.328.

See the case study and full changelog.