Mirrors/bevy
2
0
Fork 0
mirror of https://github.com/bevyengine/bevy synced 2024-11-10 07:04:33 +00:00
Code Issues Projects Releases Packages Wiki Activity

Clean up advice on glob imports in style guide (#4644)

Browse source 
# Objective

- Example was misleading, as we never import `bevy` itself in the engine (except in integration tests).

## Solution

- Clean up wording.

## Context

Noticed by @mockersf in #4608.
This commit is contained in:
Alice Cecile 2022-05-02 18:45:00 +00:00
parent 5ca78b1e27
commit 241a61d2a5
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.github/contributing/engine_style_guide.md vendored
View file

@ -6,7 +6,7 @@ For more advice on contributing to the engine, see the [relevant section](../../
## General guidelines
1. Prefer granular imports over glob imports of `bevy::prelude::*` and `bevy::sub_crate::*`.
1. Prefer granular imports over glob imports like `bevy_ecs::prelude::*`.
2. Use a consistent comment style:
1. `///` doc comments belong above `#[derive(Trait)]` invocations.
2. `//` comments should generally go above the line in question, rather than in-line.