Construct ResourceAsset and BundleAsset by hand

[aleqdev]

Is there any reason for fields of these wrappers being pub(crate)?
If there is, perhaps ResourceAsset::new(...) and BundleAsset::new(...) could still be added?

[termisaal]

skill issue as always

[kgv]

Is there any reason for fields of these wrappers being pub(crate)? If there is, perhaps ResourceAsset::new(...) and BundleAsset::new(...) could still be added?

They're marked pub(crate) because it's not obvious to me when the end user of the library might need them. What's your use case that public modifiers were needed? Of course it is possible to add public constructors.

[aleqdev]

I have a custom asset loading system which is independent of AssetServer. But the only possible way to construct ResourceAsset and BundleAsset is implemented in this function:

bevy_fluent/src/assets/bundle.rs

Line 21 in 64f90c7

async fn load(data: Data, load_context: &mut LoadContext<'_>) -> Result<()> {

which uses LoadContext and also is private