-
Notifications
You must be signed in to change notification settings - Fork 23
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
Feat: remove wild DeepL keys #54
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello HernandoR, Thank you for your first PR contribution 🎉 HernandoR
It's okay to remove the wild key, but it's not friendly for those users who can't use the official key. Can you add a DeepL custom endpoint option so that users can use DeepL third-party services, such as DeepLX? |
@HernandoR I have added Custom DeepL API URL, I have done all the work related to it, your commit code will cause conflict, please revert it. |
ecccab2
to
e7024b7
Compare
* chore: remove wild DeepL support * fix: show error toast when DeepL failed * perf: remove all wild DeepL api keys * perf: do not check DeepL API key valid * feat: enable to use custom DeepL API URL * docs: update README --------- Co-authored-by: tisfeng <[email protected]>
Seems good to me |
Wild deepL keys from github is immoral and potentially illegal.