Age | Commit message (Collapse) | Author |
|
- Removed empty paragraphs in XML.
- Consistently use bold style for "Example:", on a new line.
- Fix usage of `[code]` when hyperlinks could be used (`[member]`, `[constant]`).
- Fix invalid usage of backticks for inline code in BBCode.
- Fix some American/British English spelling inconsistencies.
- Other minor fixes spotted along the way, including typo fixes with codespell.
- Don't specify `@GlobalScope` for `enum` and `constant`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change case of "s" letter : "string" does not compile but "String" does (for gdScript)
|
|
|
|
This makes it easier to spot syntax errors when editing the
class reference. The schema is referenced locally so validation
can still work offline.
Each class XML's schema conformance is also checked on GitHub Actions.
|
|
|
|
|
|
|
|
|
|
Fix typo with example variable name in Dictionary docs
|
|
|
|
example
|
|
|
|
|
|
For the time being we don't support writing a description for those, preferring
having all details in the method's description.
Using self-closing tags saves half the lines, and prevents contributors from
thinking that they should write the argument or return documentation there.
|
|
|
|
And move GLTF docs to its module folder.
|
|
|
|
|
|
- Mention Lua-style syntax.
- Make the code samples self-contained.
- Mention caveat with `const` (also in Array).
- Clarify the description of `size()`.
This closes https://github.com/godotengine/godot-docs/issues/4272.
|
|
|
|
Change DocData comparators for MethodDoc and ArgumentDoc to get a better
ordering of constructors.
|
|
Includes:
* Decal
* Dictionary
* Directory
* DisplayServer
* DTLSServer
* DynamicFont
* EditorImportPlugin
* EditorPlugin
* EditorScenePostImport
* EditorScript
* EditorSettings
* EditorTranslationParserPlugin
* Engine
* Expression
Co-authored-by: Aaron Franke <arnfranke@yahoo.com>
|
|
|
|
This makes them display in a nicer way in the editor help.
(The title will display instead of the full URL.)
|
|
This also clarifies the `in` operator behavior in Object.
|
|
See https://github.com/godotengine/godot/issues/27615.
|
|
See #38792.
|
|
in Dictionary class documentation.
|
|
This closes https://github.com/godotengine/godot-docs/issues/3376.
|
|
* Added additional clarification for the function of the 'deep'
parameter in the Dictionary's `duplicate` method.
|
|
Fix wrong binding after #37111.
|
|
Co-authored-by: Bojidar Marinov <bojidar.marinov.bg@gmail.com>
|
|
Part of those seem bogus, methods like Array.back()/front()
should return a Variant and not void.
|
|
|
|
We already removed it from the online docs with #35132.
Currently it can only be "Built-In Types" (Variant types) or "Core"
(everything else), which is of limited use.
We might also want to consider dropping it from `ClassDB` altogether
in Godot 4.0.
|
|
|
|
- Add some missing descriptions.
- Add links to tutorials for ARVR and AnimationTree.
- Style fixes.
- Engine changes:
* Make `AnimationNodeTransition.input_<number>` properties internal
so that they don't appear in the docs. They still appear in the
inspector based on the actual number of inputs requested.
* Drop unimplemented `CPUParticles.flatness`. It's only used for 3D
particles in `ParticlesMaterial`, and thus only relevant for
`CPUParticles3D`.
|
|
I improved dictionary description to ad some real life examples and expand on it a little bit so person who never seen dictionary can understand it better seeing them for a first time here.
I also added note about the way to compare dictionaries as it can catch people of guard because common assumption is that it works the same as comparing Arrays when it does not.
|
|
See #27615.
|
|
- Document a few more properties and methods
- Add more information to many classes
- Fix lots of typos and gramar mistakes
- Use [code] tags for parameters consistently
- Use [b] and [i] tags consistently
- Put "Warning:" and "Note:" on their own line to be more visible,
and make them always bold
- Tweak formatting in code examples to be more readable
- Use double quotes consistently
- Add more links to third-party technologies
|
|
In many of the XML files it had been noted that when the documentation
refers to a return value, both "Return" and "Returns" are used. This
has now been fixed to only say "Returns".
Fixes #28867
|
|
|
|
Consistently wrap booleans in [code]
|