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

Sort assets by most recently supported Bevy version #297

Open
ItsDoot opened this issue Mar 6, 2023 · 4 comments
Open

Sort assets by most recently supported Bevy version #297

ItsDoot opened this issue Mar 6, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@ItsDoot
Copy link

ItsDoot commented Mar 6, 2023

As the Assets page grows, it becomes notably harder to sort through the assets that are actually usable with a recent or current Bevy version. IMO, the page would be well suited to sorting by assets which have been more recently updated to the current Bevy version. Especially when there are Assets among them which only work on very old Bevy versions.

@doonv
Copy link
Contributor

doonv commented Jan 5, 2024

This would require making everyone add a version key to their toml. Which will be a lot of work, but it will be possible

@alice-i-cecile
Copy link
Member

We can also sort assets without a version to the bottom.

@doonv
Copy link
Contributor

doonv commented Jan 5, 2024

We can also sort assets without a version to the bottom.

We should still make some kind of announcement when we implement the version sorting so that the assets get updated with the correct version.

@james7132
Copy link
Member

I'm running into this with bevy_system_graph, which is now deprecated as a whole, due to the changes in Schedule V3. I don't want to remove it from here because it may still be usable for older versions of the engine, but it's not being maintained or updated anymore from engine release to release.

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

No branches or pull requests

4 participants