Skip to content

test(emit-rust): add nullable list emitter coverage #690

Description

@flyingrobots

Summary

Add one focused Rust emitter test for a GraphQL field that combines list and nullability syntax, such as [String]! or [String!].

Scope

  • Primary file: crates/wesley-emit-rust/src/lib.rs
  • Avoid production-code changes unless the new test exposes a real bug.

Acceptance Criteria

  • The test uses a tiny schema string or existing local helper pattern.
  • The assertion checks the generated Rust type shape for the selected list/nullability case.
  • cargo test -p wesley-emit-rust passes.

Notes

This is a starter emitter-test task. Keep the schema generic and domain-free.

Activity

  1. added
    testsTest suite and coverage
    v0.3.0Scheduled work for the v0.3.0 release.
    on Jul 4, 2026
  2. coderabbitai commented on Jul 4, 2026

    @coderabbitai
    🔗 Related PRs

    #499 - test(stack): add Stack Witness 0001 fixture artifact shape [merged]
    #513 - expand parity fixture coverage [merged]
    #618 - feat: LE binary Rust codec emitter (le-binary-rust) + output-object codecs [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomerstestsTest suite and coveragev0.3.0Scheduled work for the v0.3.0 release.work-in-progressMethod issue is actively being worked

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions