123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251 |
- .. _doc_gdscript_documentation_comments:
- GDScript documentation comments
- ===============================
- In GDScript, comments can be used to document your code and add descriptions to the
- members of a script. There are two differences between a normal comment and a documentation
- comment. Firstly, a documentation comment should start with double hash symbols
- ``##``. Secondly, it must immediately precede a script member, or for script descriptions,
- be placed at the top of the script. If an exported variable is documented,
- its description is used as a tooltip in the editor. This documentation can be
- generated as XML files by the editor.
- Documenting a script
- --------------------
- Comments documenting a script must come before any member documentation. A
- suggested format for script documentation can be divided into three parts.
- - A brief description of the script.
- - Detailed description.
- - Tutorials.
- To separate these from each other, the documentation comments use special tags.
- The tag must be at the beginning of a line (ignoring preceding white space) and must
- have the format ``@``, followed by the keyword, and finishing with a colon.
- Tags
- ~~~~
- +-------------------+--------------------------------------------------------+
- | Brief description | No tag and lives at the very beginning of |
- | | the documentation section. |
- +-------------------+--------------------------------------------------------+
- | Description | Use one blank line to separate the description from |
- | | the brief. |
- +-------------------+--------------------------------------------------------+
- | Tutorial | | ``@tutorial:`` |
- | | | ``@tutorial(The Title Here):`` |
- +-------------------+--------------------------------------------------------+
- For example:
- ::
- extends Node2D
- ## A brief description of the class's role and functionality.
- ##
- ## The description of the script, what it can do,
- ## and any further detail.
- ##
- ## @tutorial: https://the/tutorial1/url.com
- ## @tutorial(Tutorial2): https://the/tutorial2/url.com
- .. warning::
- If there is any space in between the tag name and colon, for example
- ``@tutorial :``, it won't be treated as a valid tag and will be ignored.
- .. note::
- When the description spans multiple lines, the preceding and trailing white
- spaces will be stripped and joined with a single space. To preserve the line
- break use ``[br]``. See also `BBCode and class reference`_ below.
- Documenting script members
- --------------------------
- Documentation of a script member must immediately precede the member or its
- annotations if it has any. The exception to this is enum values whose description should
- be on the same line as the enum for readability.
- The description can have more than one line but every line must start
- with the double hash symbol ``##`` to be considered as part of the documentation.
- The script documentation will update in the editor help window every time the
- script is updated. If any member variable or function name starts with an
- underscore, it will be treated as private. It will not appear in the documentation and
- will be ignored in the help window.
- Members that are applicable for documentation:
- - Inner class
- - Constant
- - Function
- - Signal
- - Variable
- - Enum
- - Enum value
- Example
- -------
- ::
- extends Node2D
- ## A brief description of the class's role and functionality.
- ##
- ## The description of the script, what it can do,
- ## and any further detail.
- ##
- ## @tutorial: https://the/tutorial1/url.com
- ## @tutorial(Tutorial2): https://the/tutorial2/url.com
- ## The description of a constant.
- const GRAVITY = 9.8
- ## The description of a signal.
- signal my_signal
- ## This is a description of the below enums. Note below that
- ## the enum values are documented on the same line as the enum.
- enum Direction {
- UP = 0, ## Direction up.
- DOWN = 1, ## Direction down.
- LEFT = 2, ## Direction left.
- RIGHT = 3, ## Direction right.
- }
- ## The description of a constant.
- const GRAVITY = 9.8
- ## The description of the variable v1.
- var v1
- ## This is a multiline description of the variable v2.[br]
- ## The type information below will be extracted for the documentation.
- var v2: int
- ## If the member has any annotation, the annotation should
- ## immediately precede it.
- @export
- var v3 := some_func()
- ## As the following function is documented, even though its name starts with
- ## an underscore, it will appear in the help window.
- func _fn(p1: int, p2: String) -> int:
- return 0
- # The below function isn't documented and its name starts with an underscore
- # so it will treated as private and will not be shown in the help window.
- func _internal() -> void:
- pass
- ## Documenting an inner class.
- ##
- ## The same rules apply here. The documentation must
- ## immediately precede the class definition.
- ##
- ## @tutorial: https://the/tutorial/url.com
- class Inner:
- ## Inner class variable v4.
- var v4
- ## Inner class function fn.
- func fn(): pass
- BBCode and class reference
- --------------------------
- The editor help window which renders the documentation supports :ref:`bbcode <doc_bbcode_in_richtextlabel>`.
- As a result it's possible to align and format the documentation. Color texts, images, fonts, tables,
- URLs, animation effects, etc. can be added with the :ref:`bbcode <doc_bbcode_in_richtextlabel>`.
- Godot's class reference supports BBCode-like tags. They add nice formatting to the text which could also
- be used in the documentation. See also :ref:`class reference bbcode <doc_class_reference_bbcode>`.
- Whenever you link to a member of another class, you need to specify the class name.
- For links to the same class, the class name is optional and can be omitted.
- Here's the list of available tags:
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | Tag and Description | Example | Result |
- +======================================+=========================================+======================================================================+
- | | ``[Class]`` | ``Move the [Sprite2D].`` | Move the :ref:`class_Sprite2D`. |
- | | Link to class | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[annotation Class.name]`` | ``See [annotation @GDScript.@export].`` | See :ref:`@GDScript.@export <class_@GDScript_annotation_@export>`. |
- | | Link to annotation | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[constant Class.name]`` | ``See [constant @GlobalScope.KEY_F1].`` | See :ref:`@GlobalScope.KEY_F1 <class_@GlobalScope_constant_KEY_F1>`. |
- | | Link to constant | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[enum Class.name]`` | ``See [enum Mesh.ArrayType].`` | See :ref:`Mesh.ArrayType <enum_Mesh_ArrayType>`. |
- | | Link to enum | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[method Class.name]`` | ``Call [method Node3D.hide].`` | Call :ref:`Node3D.hide() <class_Node3D_method_hide>`. |
- | | Link to method | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[member Class.name]`` | ``Get [member Node2D.scale].`` | Get :ref:`Node2D.scale <class_Node2D_property_scale>`. |
- | | Link to member | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[signal Class.name]`` | ``Emit [signal Node.renamed].`` | Emit :ref:`Node.renamed <class_Node_signal_renamed>`. |
- | | Link to signal | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[theme_item Class.name]`` | ``See [theme_item Label.font].`` | See :ref:`Label.font <class_Label_theme_font_font>`. |
- | | Link to theme item | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[param name]`` | ``Takes [param size] for the size.`` | Takes ``size`` for the size. |
- | | Formats a parameter name (as code) | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[br]`` | | ``Line 1.[br]`` | | Line 1. |
- | | Line break | | ``Line 2.`` | | Line 2. |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[b]`` ``[/b]`` | ``Some [b]bold[/b] text.`` | Some **bold** text. |
- | | Bold | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[i]`` ``[/i]`` | ``Some [i]italic[/i] text.`` | Some *italic* text. |
- | | Italic | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[kbd]`` ``[/kbd]`` | ``Some [kbd]Ctrl + C[/kbd] key.`` | Some :kbd:`Ctrl + C` key. |
- | | Keyboard/mouse shortcut | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[code]`` ``[/code]`` | ``Some [code]monospace[/code] text.`` | Some ``monospace`` text. |
- | | Monospace | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- | | ``[codeblock]`` ``[/codeblock]`` | *See below.* | *See below.* |
- | | Multiline preformatted block | | |
- +--------------------------------------+-----------------------------------------+----------------------------------------------------------------------+
- .. note::
- 1. Currently only :ref:`class_@GDScript` has annotations.
- 2. ``[code]`` disables BBCode until the parser encounters ``[/code]``.
- 3. ``[codeblock]`` disables BBCode until the parser encounters ``[/codeblock]``.
- .. warning::
- Use ``[codeblock]`` for pre-formatted code blocks. Inside ``[codeblock]``,
- always use **four spaces** for indentation (the parser will delete tabs).
- ::
- ## Do something for this plugin. Before using the method
- ## you first have to [method initialize] [MyPlugin].[br]
- ## [color=yellow]Warning:[/color] Always [method clean] after use.[br]
- ## Usage:
- ## [codeblock]
- ## func _ready():
- ## the_plugin.initialize()
- ## the_plugin.do_something()
- ## the_plugin.clean()
- ## [/codeblock]
- func do_something():
- pass
|