Skip to content

Add clippy lint rules to workspace #159

@Emrys02

Description

@Emrys02

Contribution Guide

  • PRs go to the dev branch, not main
  • Application must explain your specific approach to this task; generic applications will not be assigned
  • PR description must clearly describe what you built and changed
  • Link your PR to the correct issue number

To maintain code quality and consistency across the project, we should define a set of shared clippy lint rules at the workspace level.

Implementation Guidelines Key Files: Cargo.toml.

Expectations What done looks like: The workspace Cargo.toml contains a [workspace.lints.clippy] section, and cargo clippy runs cleanly across all crates.

For any question, reach me on Discord: emry_ss

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave program

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions