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.

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

UnityNuGet usage removal #57

Open
bdovaz opened this issue Mar 13, 2024 · 1 comment
Open

UnityNuGet usage removal #57

bdovaz opened this issue Mar 13, 2024 · 1 comment

Comments

@bdovaz
Copy link
Contributor

bdovaz commented Mar 13, 2024

@mayuki Honestly I am disappointed that you have thrown away all my work that took so long to merge (#54) without creating an issue first and at least checking it with me in case I could help before making this drastic change....

With this change you may have broken the integration with OpenUPM and those of us who use UnityNuGet with OpenUPM may start having problems with conflicts and duplications.

@mayuki
Copy link
Member

mayuki commented Mar 13, 2024

I apologize for potentially disrupting your work. But this change only impacts the contents of the .unitypackage.

Originally, the instructions were to install YetAnotherHttpHandler.Dependencies via UnityNuGet, with no dependencies on YetAnotherHttpHandler itself. And there are currently no plans to change this. YetAnotherHttpHandler.Dependencies for UnityNuGet will remain.

We believe that if using OpenUPM or UnityNuGet, dependencies should be installed from there and should not be resolved by the Package contained in the .unitypackage.
We think it is preferable to use YetAnotherHttpHandler.Dependencies to resolve them from those package registries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants