Update CodePathTracerRule docs to match new API - #29
Conversation
📝 WalkthroughWalkthroughUpdates KDoc/usage examples in CodePathTracerRule.kt to reflect API rename from CodePathTracerRule.builder()/build() to CodePathTracer.Builder()/asJUnitRule(), including chaining of filter and formatter. No code logic, signatures, or runtime behavior changed. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
Status, Documentation and Community
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
code-path-tracer/src/main/kotlin/io/github/takahirom/codepathtracer/CodePathTracerRule.kt (1)
15-33: Nit: mark code fences as Kotlin for better readability.Use ```kotlin to enable syntax highlighting in rendered KDoc.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
code-path-tracer/src/main/kotlin/io/github/takahirom/codepathtracer/CodePathTracerRule.kt(1 hunks)
🔇 Additional comments (1)
code-path-tracer/src/main/kotlin/io/github/takahirom/codepathtracer/CodePathTracerRule.kt (1)
17-21: No change needed to the JUnit4 rule snippet JUnit4 supports method-level rules via@Ruleon the getter, so the existing@get:Ruleexample in your KDoc works as-is.Likely an incorrect or invalid review comment.
What
Update documentation comments in CodePathTracerRule.kt to reflect the current API pattern
Why
The documentation was outdated - it showed the old builder pattern (CodePathTracerRule.builder()) instead of the new unified API (CodePathTracer.Builder().asJUnitRule())