-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Remove LoadedAsset::meta #15485
Copy link
Copy link
Closed
Labels
A-AssetsLoad files from disk to use for things like images, models, and soundsLoad files from disk to use for things like images, models, and soundsC-FeatureA new feature, making something new possibleA new feature, making something new possibleD-TrivialNice and easy! A great choice to get started with BevyNice and easy! A great choice to get started with BevyS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!X-ContentiousThere are nontrivial implications that should be thought throughThere are nontrivial implications that should be thought through
Metadata
Metadata
Assignees
Labels
A-AssetsLoad files from disk to use for things like images, models, and soundsLoad files from disk to use for things like images, models, and soundsC-FeatureA new feature, making something new possibleA new feature, making something new possibleD-TrivialNice and easy! A great choice to get started with BevyNice and easy! A great choice to get started with BevyS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!This issue is ready for an implementation PR. Go for it!X-ContentiousThere are nontrivial implications that should be thought throughThere are nontrivial implications that should be thought through
What problem does this solve or what need does it fill?
This field is (nearly) unused, and inaccessible. It adds more conceptual overload for no advantage.
What solution would you like?
Delete the field!
Additional context
This may be planned feature work, but I don't think so. Subassets having metadata doesn't make much sense as far as I can tell, and the root asset has its metadata passed in and it isn't changed. The only part that's a little confusing is the
populate_hashesargument, but that only affects the loader dependencies, not the asset'smetafield.