Skip to content

Consider using testing.Testing to prevent non-testing purpose #378

Open
@ccoVeille

Description

@ccoVeille

I followed:

I found these comments very interesting:

I think testing.Testing could be used to prevent the usage of the lib out of test purpose.

I'm unsure about the implementation. A panic seems an option, but we can be more creative.

It might be a breaking change, but why not after all.

It might help to sort out future issues like:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions