-
Notifications
You must be signed in to change notification settings - Fork 109
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.
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
Future of tasty-hunit #388
Comments
As a general note, vendoring Personally, I try to only vendor internal dependencies, that do not leak to the public API of a package. That way users are not confronted with multiple, mutually incompatible, versions of an API. YMMV. However, there is a difference between vendoring and forking. When you fork a package, it is common practice to use a different name for that fork, so that I as a user have an easy way to understand what I am getting. This is a friendly request to follow this common practice. |
There is a third option: not re-exporting |
I have a handful of uses of |
Status quo when |
True; and to be honest, I also don't really have an issue with it staying the way it is. Maybe we just leave it as is and make it clear that |
I'm a very happy user of tasty-hunit and I don't see myself using HUnit outside of tasty. |
I also use |
Looks like this decision is still kind of open. If someone new wanted to make themselves useful around the tasty-hunit library, what would you suggest? |
There are all sorts of feature requests for
tasty-hunit
: https://github.com/UnkindPartition/tasty/issues?q=is%3Aissue+is%3Aopen+label%3Atasty-hunitYet all of them are stalled, because we are undecided whether to carry on with
tasty-hunit
including a fork ofHUnit
or makingtasty-hunit
just a test provider, re-exportingHUnit
proper. See #327 (comment) for discussion. Re-exportingHUnit
is aesthetically pleasing and less to maintain, but on the other side we'll lose a chance to make any improvements unless upstream implements them.We also need someone to own
tasty-hunit
. I, for instance, almost never use it and thus cannot judge which changes are beneficial and which are not.@andreasabel @VictorCMiraldo @martijnbastiaan and anyone else who reads this, would you like to own
tasty-hunit
and make decisions about its future?The text was updated successfully, but these errors were encountered: