Bevy ECS naming convention

[afonsolage]

I know this topic has been discussed before o Discord, but I think it's a good idea to also keep it on GitHub Discussions. Also I would like to address a more general discussion about bevy naming convention.

First of all, the idea isn't to force users or core/members devs to use this naming convention, but instead give some guidance nor share some personal preferences to newcomers.

Also bevy is in too early stage to have a style guide or something like that, so that's not the point here.

That being said, most things created by users is either struct/enum or function, where each one can be:

• struct/enum
  • Component
  • Resource
  • Event
  • State
  • SystemLabel
• function
  • system
  • startup_system
  • run_criteria

After reading some examples and users projects I noticed that some folks (don't know how often, tho) use some conventions:

• Event suffix for events
• State suffix for states
• _system suffix for system functions
• setup_ or build_ prefix for startup functions

I would like to hear any thoughts or experience about using naming conventions, what have you folks been using and think what works and what doesn't works.

For me, I'm willing to use:

• Component - nothing (Position, Health)
• Resource - Res suffix (ScoreRes, TextureRes)
• Event - Event suffix (WinEvent, HitEvent)
• State - State suffix (GameState, ManuState)
• SystemLabel - Label suffix (LoadLabel, PipelineStepLabel)
• System - _system suffix (navigate_system, player_move_system)
• Startup System - setup_ prefix (setup_textures, setup_score)
• Run Criteria - is_ / can_ / should_ / has_ something like bool variable naming convention (is_under_water, can_build)