Skip to content

verify if mpc-call-args crate is needed after integrating with codebase #3696

Description

@kevindeforth

Background

In #3684, we introduced the mpc-call-args crate. At the time, we weren't sure where the best place for that struct would be, thus, we put it into a single, small crate.

Once we use the struct throughout the codebase, we should re-visit that decision and potentially move it to a different crate.

User Story

As a dev, I like to know that all crates have purpose.

Acceptance Criteria

Decide if mpc-call-args can be kept as a standalone crate, or if it should be integrated with an existing crate.

Resources & Additional Notes

#3684 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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