Conversation
Reviewer's GuideSwaps out the previous actions-rs/toolchain configuration for the leynos shared setup-rust action in the release CI workflow, and exposes the tokenize_markdown function in the wrap module to satisfy test dependencies. Class diagram for wrap module re-exportsclassDiagram
class wrap {
+Token
+tokenize_markdown
}
class tokenize {
+Token
+tokenize_markdown
}
wrap ..> tokenize : re-exports
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Summary by CodeRabbit
WalkthroughReplace the Rust toolchain setup step in the GitHub release workflow with a custom shared action. Add a public re-export of the Changes
Sequence Diagram(s)sequenceDiagram
participant Workflow as GitHub Workflow
participant SetupRust as setup-rust Action
participant RustEnv as Rust Toolchain
Workflow->>SetupRust: Run setup-rust action
SetupRust->>RustEnv: Install/configure Rust toolchain
RustEnv-->>SetupRust: Rust toolchain ready
SetupRust-->>Workflow: Step complete
sequenceDiagram
participant External as External Caller
participant Wrap as src/wrap.rs
participant Tokenize as tokenize module
External->>Wrap: Call tokenize_markdown
Wrap->>Tokenize: Forward call to tokenize_markdown
Tokenize-->>Wrap: Return result
Wrap-->>External: Return result
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (2)
.github/workflows/release.yml(1 hunks)src/wrap.rs(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.rs
⚙️ CodeRabbit Configuration File
**/*.rs: * Seek to keep the cyclomatic complexity of functions no more than 12.
Adhere to single responsibility and CQRS
Place function attributes after doc comments.
Do not use
returnin single-line functions.Move conditionals with >2 branches into a predicate function.
Avoid
unsafeunless absolutely necessary.Every module must begin with a
//!doc comment that explains the module's purpose and utility.Comments and docs must follow en-GB-oxendict (-ize / -our) spelling and grammar
Lints must not be silenced except as a last resort.
#[allow]is forbidden.- Only narrowly scoped
#[expect(lint, reason = "...")]is allowed.- No lint groups, no blanket or file-wide suppression.
- Include
FIXME:with link if a fix is expected.Use
rstestfixtures for shared setup and to avoid repetition between tests.Replace duplicated tests with
#[rstest(...)]parameterised cases.Prefer
mockallfor mocks/stubs.Prefer
.expect()over.unwrap()Ensure that any API or behavioural changes are reflected in the documentation in
docs/Ensure that any completed roadmap steps are recorded in the appropriate roadmap in
docs/Files must not exceed 400 lines in length
- Large modules must be decomposed
- Long match statements or dispatch tables should be decomposed by domain and collocated with targets
- Large blocks of inline data (e.g., test fixtures, constants or templates) must be moved to external files and inlined at compile-time or loaded at run-time.
Files:
src/wrap.rs
🧬 Code Graph Analysis (1)
src/wrap.rs (1)
src/wrap/tokenize.rs (1)
tokenize_markdown(150-184)
1 participant
Summary
setup-rustactiontokenize_markdowninwrapmodule so tests compileTesting
make fmtmake lintmake testhttps://chatgpt.com/codex/tasks/task_e_688bf7e0c0a08322ac64f8cccb609575
Summary by Sourcery
Switch the release workflow to the leynos setup-rust action and re-export tokenize_markdown to restore test compilation
Bug Fixes:
CI: