-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
drop legacy features #20
Comments
Thank you, @szuecs, for this issue and the corresponding PR. This is something that's been mentioned to me before and there was an earlier PR to remove the fork support. See: #15 (comment) I stand behind the reasoning in that comment's second paragraph and would like to add that anyone using However, if I were on the the other side of this conversation, I probably wouldn't find that explanation sufficient, as I enjoy a repository with minimal dependencies and no security warnings as well. I've even noticed a project or two that has refrained from importing I've come around to thinking that there needs to be an option ready with minimal dependencies for the latest version of The upstream PR is ongoing, but nobody has touched it in about two weeks. If people are in favor of this, I would appreciate it if they would react on the upstream PR with a positive emoji 👍 to their show support. Or a negative one to show their opposition! 👎 I planned on moving the project at this path to Here's my plan: |
@szuecs Please see the |
@MicahParks thanks!! |
I deleted my repository, because I was not sure how you decide, so I worked on making it ok for our project, but now I just need to increase the version, thanks ! |
Glad to hear that 😄 |
We get this alert because of a dependency in this project to a vulnerable library:
The text was updated successfully, but these errors were encountered: