You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we consider renaming this crate as long as it's not widely used yet? I find the name bevy_loading misleading, because loading is only one use case, while the functionality the crate offers is progress tracking in general. This can be applied to loading, but also to (terrain-) generation, connection, or simple task tracking.
How about bevy_progress_tracking?
The text was updated successfully, but these errors were encountered:
Hmm, how would such a rename even be handled gracefully?
I guess release a new version under the old name, that just produces a compiler error telling ppl about the rename (and also a readme pointing to the rename). And then continue to squat the old name until someone has a better use for it and reaches out to ask for it.
Can we consider renaming this crate as long as it's not widely used yet? I find the name
bevy_loading
misleading, because loading is only one use case, while the functionality the crate offers is progress tracking in general. This can be applied to loading, but also to (terrain-) generation, connection, or simple task tracking.How about
bevy_progress_tracking
?The text was updated successfully, but these errors were encountered: