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

Require a crate field for every asset that is a crate #458

Open
benfrankel opened this issue Jul 16, 2024 · 1 comment
Open

Require a crate field for every asset that is a crate #458

benfrankel opened this issue Jul 16, 2024 · 1 comment

Comments

@benfrankel
Copy link
Contributor

This will help determine an accurate "latest supported Bevy version" for every crate. Related issue: #297.

Some assets have multiple crates, in which case any one of them can be used.

@benfrankel
Copy link
Contributor Author

benfrankel commented Aug 20, 2024

Current status:

  • Some crates in Bevy Assets have not been released on crates.io, so they still have no crate = "..." field. Every other crate now has a crate field.
  • crate is an optional field for now to accommodate those unreleased crates. Making it a required field is blocked on Question: How should these crates be handled? #457.
  • New crates that are added to Bevy Assets ought to include a crate field.

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

1 participant