Skip to content

fix: correct InterpreterCallerMeta.desc doc comment and 'feild' typos - #270

Open
thedavidmeister wants to merge 1 commit into
mainfrom
2026-08-25-issue-196
Open

fix: correct InterpreterCallerMeta.desc doc comment and 'feild' typos#270
thedavidmeister wants to merge 1 commit into
mainfrom
2026-08-25-issue-196

Conversation

@thedavidmeister

@thedavidmeister thedavidmeister commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Closes #196.

InterpreterCallerMeta.desc carried a copy-paste of abi_name's doc comment —
"Name of the caller corresponding to contractName feild in the abi." — which
describes abi_name, not a free-text description field. Both comments spelled
"field" as "feild".

These doc comments are consumer-visible, not only rustdoc: schema_for! in
crates/cli/src/cli/schema/show.rs emits them as the description of each
property in the JSON schema that rain-metadata schema show prints for
interpreter-caller-v1.

  • abi_name: typo fix only, the comment was already accurate for the field it
    is on.
  • desc: replaced with a description of the field it is on, in the same shape
    as the sibling alias comment ("Alias of the caller used by Rainlang.").

Doc-only. No behaviour, validation or wire-format change; no test touched.

Relation to the other in-flight work on this file

Four other open issues target crates/cli/src/meta/types/interpreter_caller/v1.rs.
None overlaps these two lines, and none blocks or is blocked by this:

This PR touches only the two doc-comment lines inside the InterpreterCallerMeta
struct, so it merges cleanly with all four in any order.

QA

  • Discriminating tests: n/a — the diff changes only doc-comment text. Nothing in
    the suite asserts these strings (grep -rn "Name of the caller corresponding\|feild"
    matched only the two lines changed), and a doc comment is not observable to a
    Rust test; its only consumer surface is schema show output and rustdoc. A
    test that pinned the prose would pin the thing being corrected, not behaviour.
  • Mutations applied: n/a — a docs-only diff has no executable line to mutate.
  • Oracle: the field's own declaration and the issue as filed — pub desc: Description
    with #[serde(default)], a RainString free-text field, against a comment
    saying "Name of the caller corresponding to contractName", which is verbatim
    the comment on abi_name: SolidityIdentifier three lines above. The
    replacement's shape comes from the sibling alias comment, not from the code
    under change.
  • Category check: issue asks (a) desc's comment describes a different field,
    (b) feild typo on the desc comment, (c) feild typo on the abi_name
    comment. Covered a, b, c — and grep -rn feild over the repo now returns
    nothing, so no other instance was left behind.

Also run under nix develop: cargo test -p rain-metadata --lib interpreter_caller
— 19 passed, 0 failed; cargo fmt --check -p rain-metadata — clean. The full
suite was not run locally by request.

🤖 Generated with Claude Code

Closes #196.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 23 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 233a0850-761a-404b-8cef-bc5a76b0c29c

📥 Commits

Reviewing files that changed from the base of the PR and between 45ca96c and 39ba22f.

📒 Files selected for processing (1)
  • crates/cli/src/meta/types/interpreter_caller/v1.rs

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant