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

Add support for scanning and cleaning up plugins #47

Open
Kidbull opened this issue Feb 5, 2024 · 1 comment
Open

Add support for scanning and cleaning up plugins #47

Kidbull opened this issue Feb 5, 2024 · 1 comment
Labels
research Research required for this issue

Comments

@Kidbull
Copy link

Kidbull commented Feb 5, 2024

This plugin is really nice and it would be awesome if it also supported cleaning up plugins

@ashe23
Copy link
Owner

ashe23 commented Feb 5, 2024

I would be happy to implement that in a plugin, but there are a couple of challenges associated with cleaning assets in a plugin.

Currently, my method for detecting unused assets in a project is primarily based on the usage of primary or level assets. This means that primary assets and all their related dependencies are marked as 'used' and are never touched.

However, when it comes to plugin assets, there can be non-primary assets that are intended for use in any project. I'm facing a dilemma in determining whether such assets are unused or not.

I would greatly appreciate any proposals or suggestions regarding this issue.

I will categorize this issue as 'research,' allowing others to provide their suggestions if they have any.

@ashe23 ashe23 added the research Research required for this issue label Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research Research required for this issue
Projects
None yet
Development

No branches or pull requests

2 participants