Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to using https://github.com/stretchr/testify #129

Closed
mfridman opened this issue Sep 5, 2024 · 0 comments · Fixed by #130
Closed

Switch to using https://github.com/stretchr/testify #129

mfridman opened this issue Sep 5, 2024 · 0 comments · Fixed by #130

Comments

@mfridman
Copy link
Owner

mfridman commented Sep 5, 2024

Given how prevalent this has become across the Go ecosystem, I've given up trying to maintain a check package across all the projects I maintain.

It also reduces contributions by using something so widely used.

https://github.com/stretchr/testify
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

tests: use stretchr/testify instead of custom check package mfridman/tparse
1 participant
@mfridman