Skip to content

Mark AST deserialisation done#25

Merged
leynos merged 4 commits intomainfrom
codex/add-serde_yml-parsing-to-ast-structs
Jul 20, 2025
Merged

Mark AST deserialisation done#25
leynos merged 4 commits intomainfrom
codex/add-serde_yml-parsing-to-ast-structs

Conversation

@leynos
Copy link
Copy Markdown
Owner

@leynos leynos commented Jul 19, 2025

Summary

  • mark AST structs deserialisable in roadmap
  • document deserialisation tests
  • remove an unused footnote that broke markdownlint

Testing

  • make lint
  • make test
  • make markdownlint
  • make nixie

https://chatgpt.com/codex/tasks/task_e_687b77a4275c83228d546d99e95772ac

Summary by Sourcery

Mark AST deserialization support as complete and update documentation accordingly, including test coverage details and cleanup of markdown footnotes.

Enhancements:

  • Mark the AST structs #[derive(Deserialize)] and #[serde(deny_unknown_fields)] annotation as done in the roadmap
  • Add documentation of deserialization tests in netsuke-design.md to explain validation scenarios

Documentation:

  • Remove an unused footnote and adjust footnote formatting in the behavioural-testing-with-cucumber guide to satisfy markdownlint

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Jul 19, 2025

Reviewer's Guide

This PR updates project documentation to reflect completed AST deserialisation work, add testing details for the new parsing logic, and clean up markdown lint issues.

File-Level Changes

Change Details Files
Clean up markdown footnotes and formatting
  • Remove unused footnote 19
  • Reformat footnotes 23 and 31 for lint compliance
  • Adjust line breaks and whitespace in footnote entries
docs/behavioural-testing-in-rust-with-cucumber.md
Document AST deserialisation tests
  • Add unit test details for ast_tests.rs
  • Add behavioural test info for manifest.feature
  • Explain error handling for unknown fields
docs/netsuke-design.md
Mark AST deserialisation as done in roadmap
  • Toggle AST #[derive(Deserialize)] checklist to checked
  • Append “(done)” notation to roadmap item
docs/roadmap.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 19, 2025

Warning

Rate limit exceeded

@leynos has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 6 minutes and 41 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 5fa0a57 and ba4c5d4.

📒 Files selected for processing (4)
  • docs/behavioural-testing-in-rust-with-cucumber.md (2 hunks)
  • docs/netsuke-design.md (2 hunks)
  • docs/roadmap.md (1 hunks)
  • tests/steps/manifest_steps.rs (1 hunks)

Summary by CodeRabbit

  • Documentation

    • Added examples of manifest files and corresponding Rust ASTs, as well as a new section detailing test coverage in the Netsuke design documentation.
    • Updated the roadmap to mark the completion of a checklist item related to AST struct annotations.
    • Improved formatting and readability in the README and various documentation files.
    • Removed an outdated reference and made minor citation formatting adjustments.
  • Style

    • Corrected a minor stylistic issue in test attribute annotations.

Walkthrough

Update documentation by removing a specific citation and adjusting formatting in behavioural testing docs, add a paragraph to the design document about unit and behavioural tests for manifest deserialization, and mark a roadmap checklist item as completed to reflect the finished implementation of AST struct annotations.

Changes

File(s) Change Summary
docs/behavioural-testing-in-rust-with-cucumber.md Removed citation [^19], adjusted formatting for [^23] and [^31], no main content changes
docs/netsuke-design.md Added sections on example manifest AST and unit/behavioural tests for manifest deserialization
docs/roadmap.md Marked AST struct annotation checklist item as completed, appended "(done)"
README.md Reformatted lines for improved readability without changing content
tests/steps/manifest_steps.rs Removed trailing comma in Clippy attribute reason string, purely stylistic

Possibly related PRs

  • Format markdown documentation #22: Normalises markdown documentation formatting and line wrapping, related to citation and formatting edits.
  • Fix citation footnotes #21: Adjusts citation footnotes and formatting in the same behavioural testing documentation file.
  • Run make fmt #16: Applies formatting fixes and markdown standardisation in documentation, including behavioural testing docs.

Poem

Pages turn, citations fade,
Tests described, their roles displayed.
A roadmap box now proudly checked,
With docs and code, the team's respect.
Markdown neat, intentions clear—
Progress marches on this year!
📚✅

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch codex/add-serde_yml-parsing-to-ast-structs

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need 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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @leynos - I've reviewed your changes - here's some feedback:

  • Please verify that the AST structs in src/ast.rs have actually been annotated with #[derive(Deserialize)] and #[serde(deny_unknown_fields)] as the roadmap and docs now claim.
  • Consider extracting the new testing details in netsuke-design.md into a dedicated Testing section to keep the design narrative focused and improve readability.
  • It could be helpful to include a brief YAML example and its resulting AST in the docs to illustrate the new deserialization behavior concretely.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Please verify that the AST structs in src/ast.rs have actually been annotated with #[derive(Deserialize)] and #[serde(deny_unknown_fields)] as the roadmap and docs now claim.
- Consider extracting the new testing details in netsuke-design.md into a dedicated Testing section to keep the design narrative focused and improve readability.
- It could be helpful to include a brief YAML example and its resulting AST in the docs to illustrate the new deserialization behavior concretely.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jul 19, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 19, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@coderabbitai coderabbitai Bot added the codex label Jul 19, 2025
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5aeb422 and 14fc85c.

📒 Files selected for processing (3)
  • docs/behavioural-testing-in-rust-with-cucumber.md (2 hunks)
  • docs/netsuke-design.md (1 hunks)
  • docs/roadmap.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.md

Instructions used from:

Sources:
⚙️ CodeRabbit Configuration File

🪛 LanguageTool
docs/behavioural-testing-in-rust-with-cucumber.md

[typographical] ~1115-~1115: To join two clauses or introduce examples, consider using an em dash.
Context: ...the-common-pitfalls> [^23]: Data tables - Cucumber Rust Book, accessed on 14 July ...

(DASH_RULE)

docs/netsuke-design.md

[style] ~553-~553: Would you like to use the Oxford spelling “deserialization”? The spelling ‘deserialisation’ is also correct.
Context: ...features/manifest.feature` validate the deserialisation logic. They verify that unknown fields ...

(OXFORD_SPELLING_Z_NOT_S)

🔇 Additional comments (1)
docs/roadmap.md (1)

23-25: Bullet wraps and spelling already comply with guidelines

The new checklist entry sits within 80-column width, uses en-oxendic “serialize/deserialize” spelling, and follows existing bullet formatting. No action required.

Comment thread docs/netsuke-design.md Outdated
Comment thread docs/behavioural-testing-in-rust-with-cucumber.md Outdated
Comment thread docs/behavioural-testing-in-rust-with-cucumber.md
@leynos
Copy link
Copy Markdown
Owner Author

leynos commented Jul 19, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 19, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 14fc85c and 5fa0a57.

📒 Files selected for processing (3)
  • README.md (1 hunks)
  • docs/netsuke-design.md (2 hunks)
  • tests/steps/manifest_steps.rs (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.rs

Instructions used from:

Sources:
⚙️ CodeRabbit Configuration File

**/*.md

Instructions used from:

Sources:
⚙️ CodeRabbit Configuration File

🪛 LanguageTool
docs/netsuke-design.md

[style] ~598-~598: Would you like to use the Oxford spelling “deserialization”? The spelling ‘deserialisation’ is also correct.
Context: ...features/manifest.feature` exercise the deserialisation logic. They assert that manifests fail ...

(OXFORD_SPELLING_Z_NOT_S)


[uncategorized] ~599-~599: Possible missing comma found.
Context: ...s fail to parse when unknown fields are present and that a minimal manifest round-trips...

(AI_HYDRA_LEO_MISSING_COMMA)

🔇 Additional comments (4)
README.md (2)

3-4: Opening tagline looks good

The re-split tagline stays within the 80-column limit and avoids forbidden pronouns.
No further action needed.


9-10: Sentence merge is clear and compliant

The single-sentence description respects the 80-column rule and keeps wording free of 1st/2nd-person pronouns.
All good.

docs/netsuke-design.md (1)

496-537: Example section is well-structured

The new illustrative manifest and AST snippet improves clarity, stays within style rules, and keeps code blocks < 120 cols.
No issues.

tests/steps/manifest_steps.rs (1)

8-11: Attribute tidy-up approved

Removal of the trailing comma silences clippy without altering intent.
Looks great.

Comment thread docs/netsuke-design.md
@leynos leynos force-pushed the codex/add-serde_yml-parsing-to-ast-structs branch from 008f08f to ba4c5d4 Compare July 20, 2025 14:17
@leynos leynos merged commit 21e1558 into main Jul 20, 2025
2 checks passed
@leynos leynos deleted the codex/add-serde_yml-parsing-to-ast-structs branch July 20, 2025 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant