Skip to content
This repository was archived by the owner on Dec 29, 2021. It is now read-only.
This repository was archived by the owner on Dec 29, 2021. It is now read-only.

What should the name be for Assert::example #110

Closed
@epage

Description

@epage
Collaborator

#108 added Assert::example.

We now have

  • main_binary for running cargo run
  • cargo_binary for running cargo run --bin <name>
  • example for running cargo run --example <name>

Should example also be cargo_example?

CC @volks73 @azriel91

Activity

epage

epage commented on May 25, 2018

@epage
CollaboratorAuthor

Noticed this when adding a test for Assert:example

volks73

volks73 commented on May 25, 2018

@volks73
Contributor

I originally had example_binary but that seemed redundant/confusing, so I shortened it to just example as I figured the usage of Cargo was implied.

The cargo_example works for me and is more consistent with the other function, especially given #111, where the usage of Cargo is no longer implied. The prepended "cargo" would indicate to users that the cargo command will be used.

epage

epage commented on May 29, 2018

@epage
CollaboratorAuthor

Addressed in assert_cmd
https://github.com/assert-rs/assert_cmd
assert_cli is going to morph into a wider-focused tool, including things like assert_fs. See #41

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

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @epage@volks73

        Issue actions

          What should the name be for `Assert::example` · Issue #110 · assert-rs/assert_cli