Skip to content

Split up bevy_core #16892

@ItsDoot

Description

@ItsDoot

What problem does this solve or what need does it fill?

Title. This crate is basically a utilities crate, which we would like to avoid (bevy_utils is slowly being split up, for example). See here for its current API surface: https://docs.rs/bevy_core/latest/bevy_core/

What solution would you like?

We should:

  • Move FrameCount and its plugin to bevy_diagnostics or bevy_window
  • Move other plugins to bevy_app
  • Move everything else to bevy_ecs

What alternative(s) have you considered?

Leave it as-is.

Additional context

Related to #11478 and #16877.

Originally brought up on the Bevy Discord.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-Code-QualityA section of code that is hard to understand or changeD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!X-ContentiousThere are nontrivial implications that should be thought through

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions