Skip to content

RFC Greater customization of cargo #44

Closed
@epage

Description

@epage

Use cases

Considerations

  • The primary use case of assert_cmd is testing Rust binaries, so we should help those users
  • An entire cargo API is orthogonal to assert_cmd and would be best to be stablized outside of assert_cmd

Proposal

  • Mirror the concept of cargo run in escargot but via CargoBuild
    • CargoBuild would have a .run() method that would return a CargoRun
    • CargoRun would have .path() and .command() methods.
  • Still provide CommandCargoExt but point people to escargot for any custom behavior
  • Deprecate the cargo path functions and instead point people to escargot for those use cases.
    • Create an issue for them to be deleted as part of the 1.0 milestone

At this point, CommandCargoExt is primarily serving a low-effort path for a "getting started" user while serving as an example of how to do more complex things (via code) and pointing to more complex APIs (via docs)

Open Issues

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions