Browse Source

Fix misplaced bad example

Moved the bad example for the inferred type for functions that return super types directly after its related statement.
Lexyth 5 months ago
parent
commit
5a46a02f4b
1 changed files with 10 additions and 8 deletions
  1. 10 8
      tutorials/scripting/gdscript/gdscript_styleguide.rst

+ 10 - 8
tutorials/scripting/gdscript/gdscript_styleguide.rst

@@ -1032,6 +1032,16 @@ the function's return type. For example, ``get_node()`` cannot infer a type
 unless the scene or file of the node is loaded in memory. In this case, you
 unless the scene or file of the node is loaded in memory. In this case, you
 should set the type explicitly.
 should set the type explicitly.
 
 
+**Bad**:
+
+.. rst-class:: code-example-bad
+
+::
+
+    # The compiler can't infer the exact type and will use Node
+    # instead of ProgressBar.
+    @onready var health_bar := get_node("UI/LifeBar")
+
 **Good**:
 **Good**:
 
 
 .. rst-class:: code-example-good
 .. rst-class:: code-example-good
@@ -1052,12 +1062,4 @@ that type will be used to infer the type of the var.
 
 
 This option is also considered more :ref:`type-safe<doc_gdscript_static_typing_safe_lines>` than the first.
 This option is also considered more :ref:`type-safe<doc_gdscript_static_typing_safe_lines>` than the first.
 
 
-**Bad**:
 
 
-.. rst-class:: code-example-bad
-
-::
-
-    # The compiler can't infer the exact type and will use Node
-    # instead of ProgressBar.
-    @onready var health_bar := get_node("UI/LifeBar")