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

Deleted my packages folder... #455

Closed
rafaelbenavent opened this issue Jun 2, 2022 · 5 comments · Fixed by #511
Closed

Deleted my packages folder... #455

rafaelbenavent opened this issue Jun 2, 2022 · 5 comments · Fixed by #511

Comments

@rafaelbenavent
Copy link

This asset deleted everything in my Packages folder. I think this should be made pretty clear that it deletes things. Ideally, if the Package folder is in use, the user should be prompted to use another folder.

@jwittner
Copy link
Collaborator

jwittner commented Jun 2, 2022

Unclear on how we'd detect that the folder wasn't just out of date - in most cases the user wants the packages folder to align with the N4U packages file defines it. If we can detect that I think it's a great idea to confirm deletion. Maybe we can track it as a user preference, prompt, but have a check box to not check going forward?

Open to PRs. =)

@raspberrypuppies
Copy link

I discovered that it even deletes itself if you move it into Assets/Packages

@JoC0de
Copy link
Collaborator

JoC0de commented Jan 21, 2023

Inside the NuGet.config file you can decide where the packages should be stored. What exactly is the use case of placing files inside the same location as files that are automatically handled by a package-manager?

@warent
Copy link

warent commented Mar 8, 2023

Well I'm relieved I read this before using the package. Deleted immediately. Please consider adding this info to your README

@JoC0de
Copy link
Collaborator

JoC0de commented Mar 9, 2023

@warent but what items are you placing inside the Assets/Packages folder as long as I know it is not a "default" folder. But yes deleting files that without a notice is not expected. I think I will change the behavior.

@JoC0de JoC0de linked a pull request Apr 8, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

5 participants