Validate code tags in documentation for potential params
Adds a check to make_rst to look for matches between the text inside of the [code][/code] tag and known param identifiers. Fixes most of what was revealed.
This commit is contained in:
parent
e2e870c611
commit
391eccca76
44 changed files with 191 additions and 175 deletions
|
|
@ -20,9 +20,9 @@
|
|||
<param index="0" name="hint" type="Dictionary" />
|
||||
<description>
|
||||
Adds a custom property info to a property. The dictionary must contain:
|
||||
- [code]name[/code]: [String] (the property's name)
|
||||
- [code]type[/code]: [int] (see [enum Variant.Type])
|
||||
- optionally [code]hint[/code]: [int] (see [enum PropertyHint]) and [code]hint_string[/code]: [String]
|
||||
- [code]"name"[/code]: [String] (the property's name)
|
||||
- [code]"type"[/code]: [int] (see [enum Variant.Type])
|
||||
- optionally [code]"hint"[/code]: [int] (see [enum PropertyHint]) and [code]"hint_string"[/code]: [String]
|
||||
[b]Example:[/b]
|
||||
[codeblocks]
|
||||
[gdscript]
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue