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

When I import this package, Under the Assets folder the Packages folder all contents has been deleted, That's real unfriendly design! #402

Closed
a358003542 opened this issue Jun 19, 2021 · 4 comments · Fixed by #511

Comments

@a358003542
Copy link

When I import this package, Under the Assets folder the Packages folder all contents has been deleted, That's real unfriendly design!

@cyraid
Copy link

cyraid commented Sep 9, 2021

It was designed to be imported in Assets Folder, why would you go below that? (I'm not a collaborator just a user)

@a358003542
Copy link
Author

@cyraid Just a warning, For Some personal reason, maybe some people put his packages all organized in the /asssets/packages folder, In some case.

@cyraid
Copy link

cyraid commented Sep 10, 2021

But since it's a .unitypackage, those are to be imported in the assets folder. It even has the special folder 'editor' to put up a menu item. The case of there being an existing /assets/packages there maybe could be a warning saying the folder exists and maybe rename it to packages.bak or give a warning? I do understand why the folder would need to be wiped.

@a358003542
Copy link
Author

a358003542 commented Sep 11, 2021

@cyraid Still i think the /assets/packages folder as nuget package station name is too general, maybe there is a warning message, but maybe some user ignore it because they do not understand what's that mean or click too quickly just passed this important message.

This package's installation can be failed, but do not delete user content in the assets folder, not all unity user has the version controll habit.

@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.

2 participants