Skip to content

Commit d580827

Browse files
alice-i-cecileexjam
authored andcommitted
Clean up advice on glob imports in style guide (bevyengine#4644)
# 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 bevyengine#4608.
1 parent e39eaab commit d580827

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

.github/contributing/engine_style_guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ For more advice on contributing to the engine, see the [relevant section](../../
66

77
## General guidelines
88

9-
1. Prefer granular imports over glob imports of `bevy::prelude::*` and `bevy::sub_crate::*`.
9+
1. Prefer granular imports over glob imports like `bevy_ecs::prelude::*`.
1010
2. Use a consistent comment style:
1111
1. `///` doc comments belong above `#[derive(Trait)]` invocations.
1212
2. `//` comments should generally go above the line in question, rather than in-line.

0 commit comments

Comments
 (0)