fix(bridges): guard deprecated-alias re-exports + ontology self-impls (#589 follow-up)#590
Conversation
…#589 follow-up) PR #589 added `#[deprecated]` to the consumer-facing bridge symbols but left two internal use-sites unguarded, so `cargo clippy -- -D warnings` errored. Two same-class fixes: 1. `lance-graph-ogar/src/bridges/mod.rs` — split the re-export: the six `*Port` types + `UnifiedBridge` stay in the clean group; the six deprecated aliases (`MedcareBridge` / `OpenProjectBridge` / `RedmineBridge` / `OdooBridge` / `SmbBridge` / `WoaBridge`) move under `#[allow(deprecated)]`. (The owner flagged this as the P0; the mod.rs guard never landed because it was dropped in the #589 rebase.) 2. `lance-graph-ontology/src/bridges/{ogit,spear,sharepoint,woa}_bridge.rs` — each module IS its deprecated struct's implementation, so its own impl blocks (+ woa's `_compile_check`) reference the deprecated struct intentionally. Added module-level `#![allow(deprecated)]` to each. Consumers in other crates still get the warning. Verified: `cargo check -p lance-graph-ontology` and `cargo check -p lance-graph-ogar` both Finished with 0 deprecation warnings at the re-export / self-impl sites. The `#[deprecated]` notes still fire at genuine external consumer use-sites (the intended beacon). Out of scope (pre-existing TD-ONTOLOGY-LINT, per #589 review): the `doc_nested_refdefs` / `oxrdf::Subject` / `odoo_blueprint doc_lazy_continuation` clippy lints — separate cleanup. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EYvNjD8M8LMNYbRy3gq2FP
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughReorganizes public re-exports in ChangesBridge Deprecation Cleanup
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Fast follow-up to #589 (merged). #589 added
#[deprecated]to the consumer-facing bridge symbols but left two internal use-sites unguarded, socargo clippy -- -D warningserrors on main. The owner's 5+3 review flagged the first; verification surfaced its sibling.Two same-class fixes
1.
lance-graph-ogar/src/bridges/mod.rs— the re-export of the six aliases was unguarded (the#[allow(deprecated)]split I intended got dropped in #589's rebase, so it never landed). Split it the waylib.rsalready is:*Porttypes +UnifiedBridgestay in the clean group; the six deprecated aliases move under#[allow(deprecated)]. (This is the owner's flagged P0, verbatim.)2.
lance-graph-ontology/src/bridges/{ogit,spear,sharepoint,woa}_bridge.rs— #589 deprecated these four structs without guarding their own impl blocks, so the ontology crate self-warns (OgitBridge::registry,WoaBridge's_compile_check, etc.). Each module is its deprecated struct's implementation, so a module-level#[allow(deprecated)]is correct — internal self-reference is intentional; external consumers still get the warning.Verified
The
#[deprecated]notes still fire at genuine external consumer use-sites — the beacon is intact.Out of scope
The
doc_nested_refdefs/oxrdf::Subject/odoo_blueprint doc_lazy_continuationclippy lints are pre-existing TD-ONTOLOGY-LINT, explicitly carved out by the #589 review as unrelated. Not touched here — separate cleanup.Status
[G]— mechanical lint-correctness fix, both crates verified clean. No behaviour change, no symbol added or removed.🤖 Generated with Claude Code
https://claude.ai/code/session_01EYvNjD8M8LMNYbRy3gq2FP
Generated by Claude Code
Summary by CodeRabbit
Release Notes