Skip to content

Competing naming conventions for types #14274

Open

Description

Some traits have competing naming conventions for types within Bevy:

Trait Suffixes used Suggestion
SystemSet System, Set, Systems, no-suffix Not obvious which to choose
Primitive3d 3d, 3, 3A, no-suffix Probably fine as-is
Primitive2d 2d, 2, no-suffix Probably fine as-is
Event Event, no-suffix Probably fine as-is
ScheduleLabel Schedule, no-suffix Just rename ExtractSchedule
RenderLabel Label, no-suffix Just rename CameraDriverLabel
SystemParam Param, no-suffix Just rename UiLayoutSystemRemovedComponentParam
PluginGroup Plugins ✅ (not counting PluginGroupBuilder)
Plugin Plugin
Bundle Bundle
AppLabel App
System System
Material Material
Component no-suffix
Resource no-suffix
Command no-suffix
Asset no-suffix
States N/A ✅ (no types provided by Bevy)
EntityCommand N/A ✅ (no types provided by Bevy)

Hard to search for because no distinguishing trait:

  • Observable events
  • Marker components
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    A-Cross-CuttingImpacts the entire engineC-Code-QualityA section of code that is hard to understand or changeM-Needs-Migration-GuideA breaking change to Bevy's public API that needs to be noted in a migration guide

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions